GitHub Actions workflows stuck in Queued — cancellation fails

[tomasandrade03]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Actions Runner

Discussion Details

Hello,

I'm experiencing an issue with GitHub Actions in my private repository:

Repository: https://github.com/tomasandrade03/software-nutri-app

Pull request: https://github.com/tomasandrade03/software-nutri-app/pull/68

Two workflow runs (CI #6 and CI #7), triggered on November 11, 2026, have been stuck in "Queued" for over two hours. Neither has started executing any jobs.

I also attempted to cancel CI #6, but GitHub returned "Failed to cancel workflow."

Earlier runs completed successfully. The issue started around today's GitHub Actions service incident, but the workflows remain stuck even though GitHub Status now reports all systems operational.

Has anyone experienced this after the incident? Is there a way to clear or restart these stuck runs?

The latest workflow should validate commit 2e6c824.

Thanks!

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[tomasandrade03]

Update: I also tried the official force-cancel REST API for the older queued run (43097426728).

It returned HTTP 409 with the message:

Cannot cancel a workflow run that has not been queued yet.

However, both the GitHub UI and gh run list show the run as queued.

This suggests a mismatch between the workflow's displayed state and its internal state. The newer run (43097862433) is also still queued.

Could someone from GitHub investigate or clear these stuck runs?

[MegaShinySnivy]

Seeing the same thing in my org. I tried reaching out to GH support and got a kindly worded "go bother someone else".

Hopefully they fix this soon, I've been waiting on a website deploy for over three hours now.

[itdove]

Here my github actions in queue since todays incident https://github.com/RedHatProductSecurity/ai-guardian/actions
https://github.com/RedHatProductSecurity/ai-guardian/pull/2714/checks

[jameswagnerjr]

Same issue here. Github Support closed my ticket immediately with a link to the forums. I reopened it. This is honestly insane behavior. There was a documented incident on githubstatus.com today that affected actions. It's marked as resolved, but clearly it's not.

[itdove]

I ran

git commit --allow-empty -m "ci: retrigger checks after Actions queue incident"

git push origin <branch>

and it re-triggered all actions/checks of my PR