GitHub Actions is still broken after the incident was marked as resolved — workflows stuck in Queued, cancellation fails #212774
Replies: 4 comments 2 replies
|
💬 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. ⭐ |
|
Can confirm same issue |
|
I can't see GitHub's internal incident data, so I can't confirm whether the backlog is fully processed. Here are checks that help separate a GitHub-side problem from something in your setup. They're general, not a diagnosis.
|
Orphaned Workflow Run Requiring Backend State Reconciliation
Requesting Actions engineering to transition this orphaned database record to a terminal state. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Actions Runner
Discussion Details
GitHub Actions is still not functioning properly, despite the incident being marked as resolved.
I'm experiencing the following issues:
Queuedstate for an extended period (30+ minutes and counting).On November 11, GitHub Status acknowledged degradation affecting Actions, Copilot, Pages, and Webhooks, including a backlog of Actions jobs.
However, marking the incident as resolved does not mean the service has actually recovered for all affected users.
The workflows are still stuck, cancellation is failing, and restarting the runner has made no difference.
Could the GitHub team please clarify:
Queuedafter the incident?Please investigate and provide an update. The service is clearly not fully recovered for everyone, and marking the incident as resolved while users continue experiencing these issues is misleading.
Thanks.
All reactions