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
Description
A GitHub Actions workflow is displayed as
in_progresseven though its job steps have finished. Both normal cancellation and the REST API force-cancel endpoint return HTTP 409.Steps to reproduce
Open workflow run
41861591843.Observe that GitHub displays the workflow as "In progress".
Attempt to cancel the workflow using the GitHub UI.
Attempt force-cancel with GitHub CLI:
gh api --method POST repos/NandaGG/GlobalGamers-Web-2026/actions/runs/41861591843/force-cancelGitHub returns:
HTTP 409 — Cannot cancel a workflow run that is not in progress.Additional information
Four newer workflow runs on commit
cef6812bc4b7e67dbcaf5c6da1aad91478a458c0remain queued:The GitHub Support website also displayed a yellow GitHub Actions service status warning on November 4, 2026.
Expected behavior
The completed job should allow the workflow to reach a terminal state, or the cancellation endpoints should work. New workflow runs should receive runners normally when capacity and account limits permit.
Actual behavior
The old run remains incorrectly marked as active, cancellation returns HTTP 409, and newer jobs remain queued.
Has anyone encountered this behavior during the current Actions service degradation? Is there a recommended recovery procedure that does not require modifying the repository or creating additional workflow runs?
All reactions