Stuck GitHub Actions run cannot be cancelled (queued, zero jobs, HTTP 409) #212125
Unanswered
rubin-quiz
asked this question in
Actions
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. ⭐ |
0 replies
|
I have the same problem |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Other
Discussion Details
I have a GitHub Actions workflow run in a private repository that has remained stuck in queued status for over a month.
The run reports queued with no conclusion.
No jobs have been created.
Normal cancellation returns: Cannot cancel a workflow run that is completed.
Force cancellation returns HTTP 409: Cannot cancel a workflow run that has not been queued yet.
I disabled the affected production workflows as a precaution.
GitHub's troubleshooting documentation recommends contacting Support for this condition. However, my support ticket was closed because my account only has access to self-service support resources.
Is there a supported way for GitHub Free users to report this apparent backend state inconsistency and have the stale run cleared?
I can provide the repository and run identifiers privately if needed. Please do not trigger or rerun the production workflow.
All reactions