Actions run 37642351262 stuck queued; cancel/force-cancel return 409

[MYLEGND]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Discussion Details

Request for GitHub staff escalation

Please help escalate an apparently stuck GitHub Actions run for server-side investigation.

• Repository: https://github.com/MYLEGND/masterapp
• Run: https://github.com/MYLEGND/masterapp/actions/runs/37642351262
• Workflow: LEGEND release branch lifecycle, run #9374
• Check suite: 101972836034
• Recorded created_at and updated_at: 2026-10-07T15:07:05Z

The run still shows Queued, while the jobs endpoint returns no jobs. Repository administrator access has been verified.

Attempts already made:

• Standard cancellation: HTTP 409.
• Force cancellation: HTTP 409.
• Deletion: HTTP 403 — "Could not delete the workflow run".

The reported cancellation response says the run "has not been queued yet", contradicting the visible Queued state.

Requested resolution

Please reconcile the workflow-run/check-suite state and cancel or clear this exact stale run. We are not requesting a workflow rerun. Please confirm its final state and whether any concurrency lock or runner allocation remains. Impact on later runs and runner usage has not been established.

GitHub's troubleshooting guide specifically describes no-job runs with cancellation/force-cancellation 409 errors and directs users to Support:
https://docs.github.com/en/actions/how-tos/troubleshoot-workflows#canceling-workflows

The signed-in Support portal says technical support is not included for this account and does not offer an Actions technical ticket. What is the appropriate staff escalation path for this platform-state issue?

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

[Sagargupta16]

Nothing is locked, so there is nothing that needs clearing. Your repository is public, so this is checkable from outside: run 9374 is the only run in MYLEGND/masterapp with status queued, it has 0 jobs, and the same workflow (legend-release-lifecycle.yml, id 362222668) completed 1,391 more runs after it, 9375 through 10765 on 15 October, the last one before the workflow was disabled. The workflow file has no concurrency key, so there is no group it could block. A run with no jobs never had a runner assigned, so no runner allocation remains and nothing was billed. The 409 on cancel and force-cancel matches that: cancellation acts on jobs, and this run never got one, which is what "has not been queued yet" means.

The escalation path you are asking about does not exist on a Free account. The troubleshooting doc you linked names Support as the only way to clear a stuck run or check suite, and it is explicit that the damage case is a concurrency group being blocked, which yours is not. Support takes technical tickets on Pro, Team and Enterprise; Free accounts can open account, security and abuse tickets only, so the portal is right that there is no Actions ticket to file. Same state was reported in #211664 and #211665 this week with no staff reply.

Leave the run where it is. It is a stale record, not a lock, and this thread is the report staff can see. If the lifecycle workflow is re-enabled and a later run of it actually sits behind this one, that is the point at which the state matters, and the Pro or Team ticket is the route then.