GitHub Actions run stuck queued with zero jobs; cancel and force-cancel both report completed #210923
Unanswered
CloudDreamer31
asked this question in
Actions
Replies: 1 comment
|
💬 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. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Actions Runner
Discussion Details
I'm experiencing a stuck GitHub Actions workflow run that appears to have an inconsistent backend state.
38238112095362710278The REST API continues to report
status: queued,conclusion: null, with the originalupdated_attimestamp and zero jobs.Both of these commands fail with
Cannot cancel a workflow run that is completed:gh run cancel 38238112095 --repo CloudDreamer31/LaplacesBoxgh run cancel 38238112095 --repo CloudDreamer31/LaplacesBox --forceThe daily and weekly pricing workflows are disabled while I investigate. This run references an older worker commit, so I need to ensure it cannot unexpectedly execute.
Could GitHub Actions support investigate the inconsistent run state and either safely terminate the run or reconcile its status?
I can provide the full run URL, API responses and any additional diagnostics required.
All reactions