GitHub Community
Replies: 7 comments 13 replies
-
|
Sadly this does not always work. I'm working with a stuck action that does not respond to anything once it gets stuck. Here's a way to get things moving again in many cases using a dummy commit: |
Beta Was this translation helpful? Give feedback.
-
|
and for me! |
Beta Was this translation helpful? Give feedback.
-
|
This worked for me. Funny enough, before pushing another commit, I found this out of concern that I would have two stuck actions. Will the prior action ever get unstuck and try to run in the future? |
Beta Was this translation helpful? Give feedback.
-
|
This worked for me too, the new action run, but the previous action remains stucked. |
Beta Was this translation helpful? Give feedback.
-
|
worked for me too! Thanks mate :) |
Beta Was this translation helpful? Give feedback.
-
|
Worked like a charm. Thanks a lot for sharing this ! |
Beta Was this translation helpful? Give feedback.
-
|
This didn't work for me even a second time - I now see two stuck Actions - so I checked the GitHub Status page and saw that it showed an ongoing incident with Actions. I suspect that even in the above cases this is what was responsible, unfortunately nothing to do but wait for GitHub to resolve the incident. |
Beta Was this translation helpful? Give feedback.
-
|
Looks like it is working now. |
Beta Was this translation helpful? Give feedback.
-
|
Working for me now too, although a slow-running integration test was still failing, possibly due to latency issues, so I skipped it temporarily and plan to re-enable it in a few hours to make sure. |
Beta Was this translation helpful? Give feedback.
-
|
This is still broken, they say actions is fixed on the status page but it's still not being picked up by runners |
Beta Was this translation helpful? Give feedback.
-
|
It worked for me when I cancelled and ran again. |
Beta Was this translation helpful? Give feedback.
-
|
Been waiting 5 hours. Cancelled and tried again, still queued for 10 mins. Seems their GitHub status is wrong |
Beta Was this translation helpful? Give feedback.
-
|
Still not running even after cancelling and trying again |
Beta Was this translation helpful? Give feedback.
-
|
Whatever it is/was it looks like it had something to do with this insane, apocalyptic Microsoft outage: |
Beta Was this translation helpful? Give feedback.
-
|
stuck with queue |
Beta Was this translation helpful? Give feedback.
-
|
I can't even cancel the pending job. |
Beta Was this translation helpful? Give feedback.
-
|
same |
Beta Was this translation helpful? Give feedback.
-
|
Did any of you find a workaround? I have been trying dummy commits, the GH CLI, nothing works. I cannot remove the ones queued and cannot start new runs. |
Beta Was this translation helpful? Give feedback.
-
|
What worked for me was:
|
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
Hey all!
We 've been using GH Actions with ephemeral runners for quite long time now, without any significant problem.
During the last weeks we came up with an issue that pops up quite randomly.
Issue:
Random workflows stuck in the queue, waiting for an ephemeral runner to pick up the job. The point is that even though the workflow status is queued, we cannot view this workflow neither by an API call (filtered status=queued) nor by https://github.com/org/repo/actions?query=is:queued
Seems like the workflow is completely invisible by GH.
As a result the workflow is queued for a long time and not running.
Workaround:
Canceling the workflow and re-run it, fixes this issue.
Beta Was this translation helpful? Give feedback.
All reactions