-
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 |
Beta Was this translation helpful? Give feedback.
Replies: 27 comments 32 replies
-
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. |
Beta Was this translation helpful? Give feedback.
-
Any idea how to fix this issue? It has been three days now. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
Same here |
Beta Was this translation helpful? Give feedback.
-
I think they have deleted everything so now everything is okay. |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
Just openend this: In my case it is a single local runner - so this basically blocks any further work. |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
@softpropsI advise you to contact the support since now your running actions counted towards your quota. |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
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." |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
My actions are not working either. Trying to deploy my website through github pages, been stuck for a while now. |
Beta Was this translation helpful? Give feedback.
-
Same here, failing to cancel or run jobs "This page is taking too long to load." Still not working =( |
Beta Was this translation helpful? Give feedback.
-
Same here! |
Beta Was this translation helpful? Give feedback.
-
Lots and lots of folks seem to be experiencing this. Github status page now says problem is resolved, but jobs are still stuck in queues with no opportunity to cancel. A word from github at this point would be good. |
Beta Was this translation helpful? Give feedback.
-
We are also experiencing this, and it is blocking us from deploying. The timing could not be worse either; please update with a workaround or ETA. |
Beta Was this translation helpful? Give feedback.
-
Experiencing the same thing, we have 5 jobs that are in queue and I am unable to cancel any of the jobs. One of these is a deploy job of an older git version of code. If these get deleted I'm all good, but if something automatically kicks off we will have an older version of code deployed to production 😨 |
Beta Was this translation helpful? Give feedback.
-
Same experience |
Beta Was this translation helpful? Give feedback.
-
I'm having this issue |
Beta Was this translation helpful? Give feedback.
-
This is still an issue I've had an action running for a couple hours now and all attempts to cancel have returned an error. |
Beta Was this translation helpful? Give feedback.
-
I made an accidental release because the cancel didn't work. |
Beta Was this translation helpful? Give feedback.
-
it is still same issue. |
Beta Was this translation helpful? Give feedback.
-
We are also facing the same issue. Workflows older than 3 weeks are still in Queued state. We tried to cancel using UI, cancel as well as force-cancel APIs. All of them return the "Failed to cancel workflow run" error. Our GitHub checks are now broken completely. |
Beta Was this translation helpful? Give feedback.
I think they have deleted everything so now everything is okay.