Replies: 2 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. ⭐ |
|
These are zombie entries left over from the recent Actions incidents (Nov 4: Incident with Actions and Pages 16:05–17:01 UTC and Incident with Actions 17:40–18:16; Nov 5: Incident with Actions 16:50–17:42 — see https://www.githubstatus.com/history). Some runs created during those windows were recorded but never actually entered the runner queue, which produces exactly the impossible-looking state you found:
There's no client-side call that can clean this up — cancel and delete are both rejected server-side precisely because the run never queued. It is best treated as a stale record: no jobs means it isn't occupying a runner or billed minutes, though it can sit visibly for a while. Meanwhile you can get fresh runs through: push a new commit, or trigger the workflow manually ("Run workflow" / |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Workflow Deployment
Discussion Details
Hello GitHub Community,
I'm experiencing an abnormal GitHub Actions state in my repository:
Repository: https://github.com/leovbr/dashboardowner-demo
Affected workflow runs:
Run #68:
Troubleshooting attempts:
"Cannot cancel a workflow re-run that has not yet queued."
"Could not delete the workflow run."
Run #77 is also queued without any jobs.
Could anyone advise how to resolve this stuck workflow state? Is this potentially an orphaned workflow run or check suite that requires GitHub-side intervention?
I want to preserve all repository files, commits, and unrelated workflow runs.
Thank you.
All reactions