Queued workflow runs stuck for a week: cancel fails (409), force-cancel fails, delete returns 403 #213427
Replies: 2 comments
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
Same pattern as several other threads this week (run created, Are they hurting anything?
Why cancel and delete fail: cancel needs the run to have reached the queue, and it never did (the 409 says exactly that). Delete only accepts finished runs (hence the 403). Since no job was ever created, the automatic queue-timeout cleanup also has nothing to act on, which is probably why they never expire on their own. What you can do:
|
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Other
Discussion Details
In our repository (klubbpulsen-kommunpodden/klubbpulsen) we have 9 workflow runs that have been stuck in Queued since 11 November 2026. They were triggered by
pull_request(synchronize) on a branch whose PR has since been merged. No jobs ever started.What we tried (same result on every attempt):
POST /repos/{owner}/{repo}/actions/runs/{id}/force-cancelreturns 409: "Cannot cancel a workflow run that has not been queued yet."DELETE /repos/{owner}/{repo}/actions/runs/{id}returns 403: "Could not delete the workflow run".Example run: https://github.com/klubbpulsen-kommunpodden/klubbpulsen/actions/runs/43098537342
Our plan doesn't include technical support, so the support ticket was closed automatically.
Has anyone seen runs stuck in this state? Is there any way to clear them, or will they become deletable after two weeks, as the docs suggest? Could someone from GitHub take a look at the run records?
Thanks!
All reactions