Workflow runs stuck "queued" with 0 jobs since the Nov 11 Actions incident : can't cancel or delete #212964
Unanswered
canisinhorto
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
This comment was marked as low quality.
This comment was marked as low quality.
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
ARC (Actions Runner Controller)
Discussion Details
Two workflow runs in my private repo canisinhorto/checkout-chaos have been stuck in queued since the Actions incident of 2026-11-11 (https://www.githubstatus.com/incidents/dvy0t3mvh1lg). They were created inside the incident window and never got any jobs.
Runs (workflow "Release", triggered by a tag push):
What I see:
Re-pushing the tag after the incident started a new run that completed normally, so only these two orphaned runs are left.
Could someone on the Actions team cancel or delete these two runs? Thanks!
All reactions