Action failed to cancel

[zaherg]

Not sure what is the issue here but I can’t seems able to cancel this workflow https://github.com/linuxjuggler/laravel-mysql-test/commit/1332f47d9ea60955c91ef2f7eb34a42d0a56548c/checks?check_suite_id=247611483

Screen Shot 2019-10-02 at 10.26.19 AM.png1892×537 66.6 KB

[riker09]

I have an action that is running for two days now. I am not able to cancel it. Clicking on “Cancel run” only yields the “Failed to cancel check suite.” error as shown in the first post (attached image).

So, same here.

[zaherg]

Any idea how to fix this issue? It has been three days now.

[zaherg]

hey @chrispat  and sorry for bothering you, but is there anyone who can look at this issue? and I’ve read a few people complains about the same issue.

This is my 6th day and the job didn’t stop yet.

Thanks again.

[riker09]

I believe they (the guys at GitHub) are aware of this issue. I don’t see any harm in having a workflow in the running state for indefinite time. It most likely was killed by some garbage collection process a long time ago.

I would like to be able to immediately cancel any running workflow, however. I haven’t been able to do this with any running workflow.

[zaherg]

Right now, since they are not counting the running time, this is okay, but someone should look at it :D.

I didn’t face any problem with any actions I used, and an error in the yml file causes this one here.

[gregoil]

Same here

https://github.com/gregoil/rotest/commit/54bd1dd400e22ad03a031daa7bdd3494b64bb5fd/checks?check_suite_id=289395292

[zaherg]

I think they have deleted everything so now everything is okay.

[edy-rodrigues]

This problem happened to me 1 hour ago. I believe there was a problem with the Github Actions system

[hellohejinyu]

😿

[trent-abc]

Here's a scary thought, tried to cancel a workflow that attempts to delete things, like a runaway freight train it plows through to completion ignoring any cancellation attempts

[jserpapinto]

2024 and we have 2 workflows stuck after an outage on Github Actions..

[razortanmayshah]

Same occurred with us also. Github support team, please resolve this ASAP

[softprops]

I’ve run into this issue as well in a private repo except that an action that runs in 2s has been running for 18minutes with all workflow runs triggered by pushes after queued. 

I believe the issue might be related to trying to rerun a job that failed but needs a passing job to trigger. The rerun logic may not be accounting for the passing job and stuck in a waiting state

[bfloch]

Just openend this:

https://hub.490633.xyzmunity/t5/GitHub-Actions/Action-stuck-for-4-days-with-Local-Runner-Windows/m-p/37895#M3119

In my case it is a single local runner - so this basically blocks any further work.

[softprops]

I’ve tried a few tactics and none of them worked. I’ve tried renaming my workflow as well as completely deleting and recreating my repository (which is okay it was brand new) but still the repository workflow seemed indefinitely queued

[zaherg]

@softpropsI advise you to contact the support since now your running actions counted towards your quota.

[softprops]

A came back the next day and my workflow run queue back to normal. I can’t say what changed so know don’t know if this will happen again

[carloscortonc]

Hi! Is this still a problem on Github? After a failed action start (https://github.com/carloscortonc/cli-er/actions/runs/2921222337/attempts/1), and a re-run (https://github.com/carloscortonc/cli-er/actions/runs/2921222337/attempts/2, I only recall executing "re-run" once) both 2nd and 3rd executions hang at "queued" state, and trying to cancel latest run results in "Failed to cancel workflow."

[runxel]

Still having this issue....urgh.
EDIT: Looks like it will be force terminated 5 minutes after you hit that cancel button, even if it was not successful in the first place.

[jlaustill]

Not happening for me :(

[ettaboyle]

Hi @runxel ,

Thanks for sharing and we appreciate your patience. You can check our GitHub Status Page to see for real-time and historical data on system performance + subscribe to issues for updates.

Current Status: Investigating reports of degraded performance

[aseem-heg]

When I try to cancel a workflow - I get this screen but the workflow never gets cancelled.

[ettaboyle]

Hi @aseem-heg ,

Thanks for sharing and we appreciate your patience. You can check our GitHub Status Page to see for real-time and historical data on system performance + subscribe to issues for updates.

Current Status: Investigating reports of degraded performance

[Eric2XU]

same here... and I am fairly sure its messing up a action that otherwise has run for years every 5 mins without an issue.

[joshua-temple]

Add another one to the list.. (it normally takes 20minutes to complete)

[Eric2XU]

FWIW, I opened a support case and they were able to force close mine. They said it was due to the run being a "check suite run". No idea what that is but you can make use of the Update a check run API endpoint to close one out if found

[gianantoniopini]

I'm also facing the same issue. I tried making a cancel and force-cancel request to the REST API, but both requests fail with status 409 and message "Cannot cancel a workflow re-run that has not yet queued.". Which is confusing because my action has status "Queued" in the UI.

[meditator3]

same issue. what's going on? the github status page doesn't show any errors. this is a 4 weeks old workflow that can't be canceled.

[hdavila146]

here I have the same problem just now, the job is already complete and still in status process I try to cancel by GUI, by API none worked and the force cancel too nothing worked. is a little frustrating because this consume the credits I think... anyone got any other solution...

[osamajandali]

I have the same error and it is preventing me from deploy, I need to deploy urgently

[Ibrahom1]

it should be good now as i was doing the same. Seems like the GitHub actions and services were down for some time. You can check https://www.githubstatus.com/ they update it if there are any issues

[osamajandali]

Oh yes it is working, thanks so much for letting me know

[meditator3]

mine's still turning and turning....
i feel bad for the runner

[Justina-03]

Same here... It doesn't work even though github status says "All Systems Operational".

[tahaJemmali]

Same issue, I tried to cancel still running

[razvanabagiu89]

Same issue for me in 2025

[liquidcms]

Not sure same issue documented here, but perhaps:

I have an action which was never queued. It simply states Queued (days ago). Trying to cancel the run and i get "Failed to cancel workflow".

I am able to run other actions but any time i run this action it also gets stuck trying to queue. I suspect the first one being hung is hanging any other run of same action.

I tried the GET posted in link above. It returns 404.

[AFMiziara]

Since 2019 !!!!!!!!! We have enterprise plan on GitHub and no support either. Looks like the team is not worried at all in fixing issues, the fact that this goes on for a long time and there is no solution still is unbelievable.

[prmntr]

How is this still happening?? I tried to rerun a workflow which should take less than 30 seconds and has been queued for half an hour; even going through the API to try and cancel it yields no results.

[Ryangr0]

These are probably all different issues, just surfacing at the same place in the UI. For me, it's that the job is waiting to get picked up. It's been 2 hours. It's blocking my pipeline. I triggered another run with

concurrency:
  group: push-${{ github.branch }}
  cancel-in-progress: true

,

But that doesn't cancel it either. It did cancel other jobs of its kind that were queued up.

I can't progress doing what I was doing, because the job I need to run isn't running right now, even though I fixed the original bug I'm facing. (My github runners being out of date and refusing to pick up jobs). I can't run the job again with ubuntu-latest instead because the previous job, trying to run on my own runners, arc-runner-set, is eternally waiting to get picked up by runners that will never spawn. I'm unable to force this job to cancel for some reason that isn't being surfaced to me, the user. I hope this will resolve itself, it looks like it's completely out of my control for now?

[marcinkubica]

Problem is still there. I have product development and release affected. Please dig into the root cause.

I've used report off-topic to admins option in hope Microsoft will pay attention and fix the issue, which has been "resolved" in 2019 by "they have deleted everything". Did this as I was linked by the Github Support site when creating the ticket as a place providing resolution to my issue.

Thanks and best regards