Replies: 3 comments 9 replies
|
@jpgpi250, I haven’t seen this resolved, so these are things to try, not a fix. The two errors suggest GitHub is holding the run in an inconsistent state: the API says queued, while the cancel call treats it as completed. I’d call the endpoint directly with gh api -X DELETE repos/jpgpi250/piholemanual/actions/runs/43098457241 and post the full response body, because it may say why you get the 403. If this run came from the Pages deployment, I don’t know whether the owner can delete those. Is it blocking anything, such as a new Pages deploy? If not, an empty queued run costs nothing, which is worth saying in the support ticket. |
|
Same problem here. I think its from the Nov 11 Actions incident, so github side, not your token. I dont think you can delete it yourself, backend need to fix it. Run has no jobs so it dont use minutes and dont block new runs. Just push a new commit to check new run is working ok. Also add your run id in discussion 212780, many people put there so staff can see. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
ARC (Actions Runner Controller)
Discussion Details
GitHub Actions run permanently queued, no jobs, cannot cancel or delete (HTTP 403)
I have a GitHub Actions workflow run that has been stuck in the queued state since 11 November 2026.
Repository:
jpgpi250/piholemanualWorkflow run ID:
43098457241Direct link: https://github.com/jpgpi250/piholemanual/actions/runs/43098457241
The workflow was created when I temporarily enabled GitHub Pages deployment.
The run has never progressed and has no associated jobs.
Using GitHub CLI, I get:
Checking its jobs:
Cancellation attempts:
Web interface: cancellation fails.
GitHub CLI:
This contradicts the reported
queuedstatus.Deletion attempt:
My GitHub CLI authentication has
repoandworkflowscopes.I have already contacted GitHub Support twice, but both tickets were closed almost immediately without resolving the issue.
My question:
Is there a way to remove this orphaned workflow run, or does this require intervention by GitHub's Actions backend team?
I would appreciate advice from someone who has encountered and resolved this particular inconsistent state.
All reactions