Actions run stuck queued since 29 October — zero jobs, cancel and force-cancel return 409

[racingmodel]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

Hi everyone 👋

Small correction: I initially selected “ARC (Actions Runner Controller)” by mistake. This concerns Workflow Deployment. Could a moderator please update the topic label when convenient? Thank you!

Could someone from GitHub please help investigate a workflow run that appears to be stuck, or point me towards the right escalation route?

The run has remained Queued since 29 October 2026 at 17:07 UTC, with zero jobs created. It was still in that state when checked on 1 November at 12:50 UTC.

Public run: https://github.com/racingmodel/nfl-2026-visualizer/actions/runs/40918292299
Check suite ID: 110918601409

I have already tried:

• Cancelling through the GitHub interface, which displayed “Failed to cancel workflow”.
• The REST API cancellation endpoint.
• The REST API force-cancellation endpoint.

Both API attempts returned HTTP 409 with:

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

That seems inconsistent with the run being displayed as Queued.

GitHub’s troubleshooting documentation describes similar symptoms for an abnormal or out-of-sync run and recommends contacting Support. However, the Support portal did not offer a technical-support route for my account, so I’m asking here.

Could GitHub staff please check whether the run or associated check suite is stuck and, if appropriate, clear or terminate it? I’m requesting cleanup of the stuck run only. Please do not rerun the workflow or trigger a new deployment.

If further diagnostic information is needed, please let me know the minimum required and whether it should be provided through an official private channel.

Thank you for your time and any help you can offer!

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

[Aur-iii]

ive also got the same issue, ive had a run stuck in queue since 4am last night. just like you, i tried to go through github support but they didnt have any paths forward for me, so ive also come here! i guess ill include my stuck run since we're all in this together <3

https://github.com/Aur-iii/aurifellmusic/actions/runs/41288355789
check suite id: 111906192541

i hope we can get this resolved!

[racingmodel]

Thanks for adding your example, and sorry you’re stuck with this too!

It’s helpful to have another run showing similar symptoms. Hopefully someone from GitHub can investigate both cases and help clear the stuck runs, or point us towards a support route that can.

Really appreciate you sharing the details—hope we can both get this resolved soon 🙂