Deployment runs stuck in queued state — cancellation returns HTTP 409

[Hadimetlej]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Hello,

Two manually triggered deployment workflow runs in a private repository are stuck in the “Queued” state. They had no jobs when last checked.

Both normal cancellation and force cancellation returned HTTP 409. The deployment workflow was disabled when last checked.

What is the safest way to clear these stuck runs and confirm they cannot execute? I can share the run IDs privately with GitHub Support if needed.

I do not want to trigger a new deployment.

Thank you.

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

[Subi003]

The safest approach is to have a repository administrator or GitHub Support investigate the two run IDs and confirm the runs are canceled before taking further action. Since both cancellation methods returned HTTP 409 and the workflow is disabled, don’t try to clear the runs by re-enabling or re-running the workflow, or by triggering another deployment.

Share the run IDs privately with GitHub Support, along with the repository and workflow details and the cancellation error. Ask them to verify whether the queued runs can still be scheduled or execute, and to clear them if appropriate. Afterward, check that both runs show a terminal state such as Cancelled and that no jobs were created. A disabled workflow is useful context, but by itself it doesn’t confirm what will happen to runs that are already queued.