Workflow rerun stuck before queue after Actions outage; cannot cancel or rerun

[ericrisco]

A workflow dispatch in a public repository became internally inconsistent during the GitHub Actions major outage on 2026-08-06 and remains stuck after service recovery.

Repository: https://github.com/ericrisco/rsc-harness
Run: https://github.com/ericrisco/rsc-harness/actions/runs/31126810514
Workflow: release
Event: workflow_dispatch
Head SHA: 2c14dfbb4edede4d0b26e8804f4337c1da7784c5

Current API state:

• status: queued
• conclusion: null
• run_attempt: 1
• jobs: 0
• updated_at: 2026-08-06T19:38:47Z
• no other queued or in-progress runs exist for this workflow

Recovery attempts after GitHub Status returned to operational:

1. Normal cancel: Cannot cancel a workflow run that is completed.
2. Force cancel endpoint: HTTP 409, Cannot cancel a workflow re-run that has not yet queued.
3. Rerun: This workflow is already running.
4. Delete run: HTTP 403, Could not delete the workflow run.
5. Disable and re-enable the workflow: state remained queued with zero jobs.

Impact: the stale run owns the release concurrency group and blocks publication of @ericrisco/rsc 1.0.11. Dispatching another patch release is unsafe because the zombie run could later resume and produce an unintended second version bump. npm remains at 1.0.10; no v1.0.11 tag or GitHub Release exists.

Could GitHub staff purge or repair this rerun, or provide a safe API procedure to release the stuck concurrency state?

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.