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
ARC (Actions Runner Controller)
Discussion Details
Repository: Amnexico/VSComp
Two GitHub Actions workflow runs are stuck in “queued” status with no jobs created:
https://github.com/Amnexico/VSComp/actions/runs/43097797629
https://github.com/Amnexico/VSComp/actions/runs/43097840420
Both runs were created on November 11, 2026, around 20:44 UTC.
Cancellation through the GitHub UI fails. We also tried the standard cancellation and force-cancellation REST API endpoints. Both return HTTP 409:
“Cannot cancel a workflow run that has not been queued yet”
However, querying those same runs returns status “queued” with zero jobs.
The issue persists after the general Actions incident was marked resolved. It is blocking production deployments.
Please investigate the inconsistent run states and cancel both runs so we can start a single deployment of the latest main branch.
If this is not the correct support category, please forward this request to the GitHub Actions team.
All reactions