Runners stuck in "Waiting for a runner to pick up this job..."

[KaneTesta]

Select Topic Area

Bug

Body

Hey there,
It seems our Github runners are stuck in the Waiting for a runner to pick up this job... status. It has blocked all of our deployments for the last hour or so. Is there an outage? It has always worked up until today and we haven't changed any workflow config.

We are using a large linux runner.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[DirkLachowski]

Same here, and unfortunately this is an ongoing problem for months. Sometimes runner pick up a job in an instant - then it takes 10 minutes, then a year, then back to instant. We have a job using a mix of larger and smaller runners. The small ones pick up the jobs, the larger don't. In our case, terminating and restarting the job sometimes helps and also did today. But then, if i have to babysit the runner infra, why use runners at all?

The biggest downer is the Github's status page shining in a bright green. It's like they have no idea that the build infra is broken, and so it goes on for eternity.

[KaneTesta]

Yes definitely feel that the status page should give more insight around this...
I found that pushing a few useless commits to kick it back into gear worked, but its quite annoying having these commits in my repo

[DirkLachowski]

That maybe works because it triggers a new run. Try terminating the stuck runner, then restarting the complete job. That most of the time unstucks it on the first try.

[KaneTesta]

Yeah I did try that multiple times. Not sure why it didn't work since technically its doing the same thing

[zman0225]

Yep, experiencing the same

[markolucky7]

Experiencing the same issue with large hosted runners as of today. Can't get it to start.

The normal runners are starting fine.

Having this specific issue first time in 2y since we started using large runners.

[dungle-rg]

please help addressing this asap!

[KaneTesta]

Seems like https://www.githubstatus.com/ has finally updated acknowledging the fault. Would be awesome to hear an update

[pdparchitect]

Yep. Still stuck

[jonslo]

Experiencing this a lot today. The runners were previously working