Actions run stuck queued with zero jobs/checks; cancel 409 and dispatch 500 #207772
Unanswered
robertwylezalek-dev
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
Workflow Deployment
Discussion Details
A staging deployment workflow is stuck with contradictory scheduling/cancellation state. These are authenticated REST observations, not a diagnosis of GitHub's internal cause.
robertwylezalek-dev/bjorn-skiDeploy staging theme(workflow_dispatch,ubuntu-latest)94113044933a251651c4bfb86eef155ff9d1f1b61f369c1ff54Confirmed symptoms:
queued, withconclusion: null. Jobs:total_count: 0; check runs:total_count: 0.created_at,updated_at, andrun_started_atall equal2026-09-13T08:50:53Z. The suite timestamps are also unchanged. A check at2026-09-13T16:55:58Zstill showed the queued run/suite, zero jobs and a suite latest-check-run count of zero.Cannot cancel a workflow run that has not been queued yet.One force-cancel attempt also received HTTP 409; GitHub CLI 2.97.0 substituted its genericCannot cancel a workflow run that is completedmessage, so the raw force-cancel body is unavailable.The earlier diagnostic snapshot found no pending deployment approvals and no other active run in the repository. Both refs use the same fixed concurrency group with
cancel-in-progress: false. Required tests and deployment guards were preserved.Could GitHub staff investigate/reconcile run
34748585929and suite94113044933, investigate the dispatch HTTP 500, confirm whether either request may still begin execution, and advise a supported way to resume deployment safely?I found similar symptoms in discussions #205991 and #207496; a shared internal cause is only a hypothesis.
All reactions