Github Actions - Workflows are Queued since 15 Minutes

[TirushV]

Why are you starting this discussion?

GHA jobs are Queued

What GitHub Actions topic or product is this about?

Workflow Deployment

Discussion Details

We use GHA across our Fox organization. Currently we rely on Github enterprise actions for our App/Infra deployments. Since 10 minutes our Workflows are queued. Expecting it to be resolved ASAP.

[TirushV]

Had to wait 15 minutes long to start a workflow from queue!!

[dotJoel]

definitely something up w/ actions.
looks like they had trouble yesterday.

[sarahcthekey]

Also having issues, jobs queued

[lucasilotto]

I have the same problem, I've been waiting for 15 minutes already

[TirushV]

I waited that long and it simply cancelled the workflow. Restarted it and it's once again in queue.

Same i had stopped it exactly at 15min and retried and it queued them.

[danmichaelo]

It's on https://www.githubstatus.com/ now, but I wish they updated the status page a bit faster

[m-kildare]

looks like this issue is still happening

[nwhobart]

@m-kildare agreed.

[cristinecula]

All of our actions using self-hosted runners are queueing indefinitely.

[nwhobart]

@cristinecula same

[nwhobart]

@cristinecula if you're still having issues look at your ephemeralrunners resource in Kubernetes (assuming that's where you're running your self-hosted runners). We had several dozen that were just in a FAILED state and once we manually deleted those, our jobs started running again. Very odd.

[cristinecula]

@nwhobart Thanks! We recreated our runners and it seems to be fine now.

[manojdhimann]

@cristinecula Facing the same issue.

[chanakaeshan]

It sounds like you're experiencing delays with GitHub Actions workflows being queued for an extended period (15+ minutes) across your Fox organisation's deployments. This can be disruptive for critical app/infra deployments.

Possible Causes
GitHub Enterprise Capacity Issues: There might be temporary capacity constraints on GitHub's side

Organisation/Repository Limits
You may have hit concurrent job limits

Runner Availability
If using self-hosted runners, they might be unavailable or at capacity

Recent Changes
Any recent workflow or infrastructure modifications

Recommended Actions
Check GitHub Status (https://www.githubstatus.com/): Visit GitHub Status to see if there are ongoing incidents

Review Organisation Limits

Go to your organisation settings → Actions → Runners

Check if you're hitting any concurrency limits

Examine Runner Status

For self-hosted runners, verify they're online and healthy

For GitHub-hosted runners, check the queue position

Temporary Workaround

Consider re-running critical workflows

If possible, stagger workflow triggers to reduce queue pressure