Replies: 3 comments
|
💬 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. ⭐ |
|
Hi, This matches a pattern other users have reported for runs created around November 11: the run record exists but no jobs were ever created, so the UI cancel fails (your 422). Your run ID (43095952864) is very close to run IDs in other reports with the same symptoms, which points to a platform-side problem and not to your workflow. Community members can't clear the record, but here is what you can still try. 1. Try the API, not the UI The UI cancel calls the check suite, which is what returned 422. The run-level endpoints are different, so try them: gh api -X POST repos/Kizuzuma/Wolter/actions/runs/43095952864/cancel
gh api -X POST repos/Kizuzuma/Wolter/actions/runs/43095952864/force-cancelOther users with the same state got HTTP 409 ("has not been queued yet") from both, so this may fail too. If it does, include the exact response in your support ticket, because it helps staff identify the state. 2. Try deleting the run through the API The UI hides "Delete workflow run" for queued runs, but the API sometimes accepts it: gh api -X DELETE repos/Kizuzuma/Wolter/actions/runs/43095952864This removes only the run record, not your code, workflows or other run history. 3. Check whether it is actually blocking anything Your new
4. Escalate with the specifics Contact GitHub Support (https://support.github.com/contact, choose Actions) with:
If the ticket is closed with a referral to self-service resources, reply to it asking for human review and mention that the run has no jobs, so there is nothing a user can cancel or delete. |
|
None of these workarounds are working for me. Cancel, Force Cancel, Delete. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Other
Discussion Details
Hello GitHub team,
I have a stuck "zombie" workflow run in a private repository that has been stuck in the
Queuedstate ("Starting your workflow runs...", no jobs created) since November 11, 2026, and cannot be cancelled or deleted.Kizuzuma/Wolter(private)Deploy Cloudflare Worker(cloudflare-worker.yml)43095952864(https://github.com/Kizuzuma/Wolter/actions/runs/43095952864)116706384035What I've already tried:
"Failed to cancel workflow."(PUT /suites/116706384035/cancelreturnsHTTP 422 Unprocessable Entity).workflow_dispatchrun in the sameconcurrencygroup (cancel-in-progress: true) completed successfully, but did not cancel the stuck run.Queued, the "Delete workflow run" option is unavailable.Could someone from GitHub please force-cancel or clear this stuck workflow run on the backend? Thank you!
All reactions