GitHub Actions workflow stuck in Queued — cancellation fails #212793
Replies: 2 comments 7 replies
|
💬 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. ⭐ |
|
We're having the same issue now. we can't force cancel it either. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Actions Runner
Discussion Details
GitHub Actions workflow stuck in Queued — cancellation fails
Hello GitHub Community,
I'm experiencing a GitHub Actions issue in a private repository. A workflow triggered by a pull request update has remained in the Queued state for over an hour, without any jobs starting.
Attempts to cancel the workflow through the GitHub Actions interface return:
Failed to cancel workflow.Environment
ci.ymlpull_request(synchronize)QueuedSteps to reproduce
Failed to cancel workflow, and the execution remains queued.Expected behavior
The workflow should be assigned to runners and execute normally, or GitHub should allow the queued execution to be cancelled.
Actual behavior
No jobs start, and cancellation fails.
Additional context
The issue occurred on the same date as a reported GitHub Actions service disruption.
Previous workflow runs in the same repository completed normally. Local build, migration and automated test checks also passed on the current code.
I have not modified the workflow or pushed additional commits to work around the issue.
Questions
Any guidance would be appreciated. Thank you.
All reactions