Github action stuck at queue

I have a workflow that stuck at Queue state for a long time. I can’t even cancel the flow. Re-commit also did not help with this problem. 

8 Likes

Same here.

Builds won’t start, can’t be canceled.

Same here. :-/

I was trying to push for pushing to use it for all our projects.  I know its beta but… Not helping my case

Same here, though I have seen builds working in public repos, mine is private, not sure if that makes a difference.  Failed build (broken yml) is somehow failed and queued for the last 13 hours and the build after it is just pending and not starting.

Edit: Turns out that in my case there was still something broken with my yml file. Fixing that allows new builds to run.

Specifically I had this:

    steps:
    - uses: actions/checkout@v1
      with:
        submodules: recursive
# missing name: here 
      run: .\generate_projects.bat /vs2019

I saw the same problem. I reached out to GitHub, and it’s a known issue they are working on.

3 Likes

same here :cry:

Now my action has been working perfectly. But the 2 builds that stuck can’t be canceled or deleted. 

Do you have a link to track the issue?

1 Like

Hi, 

It’s a known issue that github is working on, please contact private support at https://support.github.com/contact, thanks.

Any news , anyone ?

thanks

2 Likes

Same here.

Even rolled back to older commit which the build was passing on, and it didn’t even run (stuck in queue!).

ALSO builds in other repositories (where I didn’t even commit, just re-ran them) are stuck in queue.

Must be a GitHub issue.

4 Likes

I’m seeing similar issues. Looks like github actions is seeing degraded performance right now. Hopefully it will clear up as this gets fixed.

Also encountering this issue, builds ultimately file to some kind of timeout. Copypasting all the error messages I’ve received here so googlers find the thread:

GitHub Actions has encountered an internal error when running your job.

There was a failure in sending the provision message: A timeout occurred while sending request to the remote provider.

There was a failure in sending the provision message: Unexpected response code from remote provider InternalServerError

Provisioning request delayed or failed to send 5 time(s). This is over the limit of 3 time(s).

I’m seeing the exact same issue right now,

hard reset to previously passing commits now fails… 

at least status.github.com shows actions as degraded

2 Likes

Same here, all builds stuck and CI failed with 

GitHub Actions has encountered an internal error when running your job.

My builds are also stuck in the queue. But fails after 15mins or so saying 

GitHub Actions has encountered an internal error when running your job.

any issue link? has it been resolved? What’s time can be considered normal? Mine has been stuck for 10 minutes for the moment, which is already weird to me.

Is this issue still occuring for everyone?

2 Likes

I’ve been getting it the last fifteen minutes

1 Like

Glad to know I’m not the only one. This issue must be coming from Github’s end

1 Like