GitHub Actions stuck queued with zero jobs — cancel 409, rerun 403, force-cancel 409 #212813
Unanswered
mrjosephpuglisi-lang
asked this question in
Actions
Replies: 1 comment
|
💬 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
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
Workflow Deployment
Discussion Details
GitHub Actions stuck queued with zero jobs — cancel 409, rerun 403, force-cancel 409
I'm experiencing an issue with two GitHub Actions deployment workflows that appear stuck in an inconsistent state. I'm using GitHub Free and would appreciate guidance, particularly if GitHub staff can investigate the backend state.
Repository:
mrjosephpuglisi-lang/tenant-forge-baseBranch:
stagingCommit:
500e3998d9e7772b7e985f149960e6bbfb63e92bAffected workflow runs:
Both runs were created on 11 November 2026 at 20:18:19 UTC.
Both have remained in
queuedstatus with:Recovery attempts
I attempted the following operations once on the Cloudflare workflow:
None succeeded, and I have not repeated them.
Other checks
ubuntu-latestrunners.staging.cancel-in-progress: false.Possible incident connection
GitHub reported an Actions incident around the same period:
https://www.githubstatus.com/incidents/dvy0t3mvh1lg
The runs were created before the published incident start and remained stuck afterward. I cannot establish whether the incident caused the problem.
Thank you for any guidance.
All reactions