GitHub-hosted runners fail to start across multiple branches – runner_id: 0

[Duppatz]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Hello GitHub Community,

I am experiencing an issue with GitHub Actions in my repository:

Repository: https://github.com/Duppatz/oda-webhook

Multiple GitHub-hosted workflow jobs are failing before any job steps execute.

The affected workflows use standard GitHub-hosted runner labels:

• "ubuntu-latest"
• "ubuntu-24.04"

The job information consistently shows:

• "runner_id: 0"
• No runner assigned
• No steps executed
• Workflow job conclusion: "failure"

Example failed runs:

• Browser QA: https://github.com/Duppatz/oda-webhook/actions/runs/42522862033
• Backend Tests: https://github.com/Duppatz/oda-webhook/actions/runs/42522339077
• ClickPesa Tests: https://github.com/Duppatz/oda-webhook/actions/runs/42522339001

This issue is not limited to one pull request or branch. We also observed successful workflow runs on "main", followed shortly by failures on "main" with the same runner allocation symptoms.

Repository settings currently allow all actions and reusable workflows, with read and write workflow permissions enabled.

There are no self-hosted runners configured. We intentionally use GitHub-hosted runners.

Could someone help determine whether this is a hosted-runner provisioning issue, an account/repository restriction, or another GitHub Actions infrastructure problem?

We would appreciate guidance on how to restore normal runner allocation.

Thank you.

[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. ⭐