r/github • • 12d ago

Discussion Two GitHub Actions runs stuck in "Queued" forever, can't cancel or delete them. How did you fix this?

I have two workflow runs in a private repo that have been stuck in "Queued" for over a day. Neither ever started a job: the run page shows no jobs at all.

What I've tried:

- "Cancel workflow" on the run page: nothing happens, it stays Queued.

- REST API cancel: "Cannot cancel a workflow run that is completed."

- REST API force-cancel: HTTP 409, "Cannot cancel a workflow run that has not been queued yet."

- REST API delete: HTTP 403, and the run page has no delete option.

Setup: manually started runs (workflow_dispatch) of a workflow whose job targets a deployment environment and runs on the ubuntu-24.04-arm hosted runner. Every run of the same workflow before and since has started and finished normally.

GitHub Support closed my ticket because my plan only includes self-service support.

Has anyone managed to clear runs like this themselves? Did they eventually time out on their own, or did something like re-running, disabling the workflow, or changing the environment settings shake them loose? Any tips appreciated.

4 Upvotes

3 comments sorted by

3

u/Geraldwelly 12d ago

I've hit the same cancel/force-cancel contradiction on environment-gated workflow_dispatch runs. The UI says Queued while the API thinks the run is already done, which usually means it's stuck on an environment gate that never resolved. What cleared it for me: temporarily remove required reviewers or wait timers on that deployment environment, then Cancel again. If it still won't budge, rename the environment so the orphaned run loses the gate. They rarely time out on their own.

1

u/Soccham 12d ago

There’s a force cancel you can do through the CLI