Replies: 5 comments 1 reply
|
💬 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. ⭐ |
|
I'm seeing the same issue across multiple workflows in one private repository, not just the deployment workflow. Three production deployment runs and two separate game-log workflow runs remain queued with empty job lists. The workflows use different concurrency groups, and the previous production run completed successfully. Canceling one queued production run from the GitHub UI failed. The runs were created within a few minutes of each other on Nov 11. GitHub Status showed all systems operational when checked. I also see more than a dozen separate Actions discussions describing similar queued runs, empty job lists, or cancellation failures, many posted within the past hour. That broader pattern makes a platform-side scheduling issue more plausible than a repository-specific configuration issue. Update: GitHub's status page later confirmed an Actions degradation within a broader incident. It reported mitigation at 4:07 PM ET, said the Actions backlog was fully processed at 4:21 PM ET, and resolved the incident. However, a run in my private repository still showed queued status and the same cancellation error at about 5:20 PM ET. I have kept repository and run identifiers private. Could GitHub staff advise how to reconcile runs that remain queued after the reported recovery? GitHub incident update |
|
Same issue with my public workflow: https://github.com/kmcclellan/kafka-di/actions/runs/43098527902 |
|
Update, November 13: a fresh API check confirms that all 21 original workflow runs remain queued. Both inspected control runs still have zero jobs. The authenticated Support portal provides no Actions technical-support category for this account. Ordinary UI cancellation previously failed; increasing the Actions budget did not resolve the issue. Could GitHub staff provide a private escalation channel and a supported recovery procedure for these existing runs? Repository and run identifiers are available privately. No force-cancellation, deletion, or replacement runs have been performed. |
|
I have 4 sitting in the queue since 11 November as well, around the time GitHub declared that incident. Cancelling via UI gives errors as described. Via API fails as well. The only work-around was an empty commit to retrigger the actions: |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
GitHub Actions — GitHub-hosted runners / workflow scheduling (not ARC)
Discussion Details
21 workflow runs in a private repository remain queued with zero jobs and no artifacts.
Actions are enabled, and the workflows use GitHub-hosted runners, not ARC or self-hosted runners. No applicable concurrency or environment approval gates were found.
Standard cancellation through the authenticated GitHub web interface returns “Failed to cancel workflow.” Increasing the Actions budget did not resolve the affected run; another ordinary cancellation attempt returned the same error.
We have not attempted force-cancellation, deleted runs, or created replacement runs.
The support portal states “Technical support not included.” Its repository contact form only offers unrelated feature categories.
Is there a supported recovery procedure or a private escalation channel for GitHub staff to inspect these stuck runs? I can provide repository and run identifiers through a private support channel.
The ARC topic was selected by mistake. Please remove the ARC label and recategorize this discussion if needed.
All reactions