Runner is stuck on ready and all actions are stuck on queued

[Avihuc]

Select Topic Area

Question

Body

I have not changed anything in my configuration nor did I max out my subscription payment, yet the runner is not working.
I've tried to add a new runner and it's stuck on "Provisioning" for a while now and I don't know what should be my next step.

[mozesma]

same issue here, started a couple of hours ago, seems to be happening when the job is set to run on a runner by label.
when changing to runs-on: ubuntu-latest it works, but that's not helping with all of the jobs.
I have created a support ticket.

[natali-avr]

Having the same issue.

[marc-barry]

@mozesma Did you get an update on your support ticket. https://www.githubstatus.com/ shows all �� but we are also seeing our entire CI system blocked as a result of this. We run all jobs by label.

[mozesma]

Unfortunately no update yet, we are blocked as well.

[marc-barry]

OK. I have went ahead and filed a support ticket as well. I don't know if these discussions are actively monitored by their support.

[Avihuc]

I've also filed a support ticket before creating this thread. Will update in case they respond.

[AnthonyAtSigma2]

We have a ticket in too. Will let you guys know if we hear something.

[sbrnunes]

Having the same problem here. It's unbelievable that this is going on for more than an hour, as it seems, and the status page is still showing all products in 🟢.

[simon-icy]

Have the same issue, what's going on? anyone got a response from Github?

[AnthonyAtSigma2]

Just got a response with a link to this: https://www.githubstatus.com/incidents/qq1m7mqcl6zk

[saadbahir]

Same here and it has been 6 hours!

[jkoeller]

I am having the exact same problem.

[chsi020]

We are experiencing the same or a similar issue. Our workflow is stuck on Waiting for a runner to pick up this job... with our custom ARM64 runner. We tried recreating the runners, but now they are stuck either in the deleting or provisioning stage.

[marc-barry]

An incident has been reported now: https://www.githubstatus.com/incidents/qq1m7mqcl6zk

[Avihuc]

It says that it's been resolved, but my workflows are still not running

[simon-icy]

I can confirm that mine are running, linux large runners

[Avihuc]

Mine are running as well now

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬