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
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.
Any idea how to fix this issue? It has been three days now.
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.
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.
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.
I think they have deleted everything so now everything is okay.
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
Just openend this:
In my case it is a single local runner - so this basically blocks any further work.
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
@softpropsI advise you to contact the support since now your running actions counted towards your quota.
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