A new way to understand your GitHub-hosted runner capacity
Explore and understand your overall GitHub-hosted Actions runner capacity with the new runner view.
We have heard from you that it was a challenge to understand why your Actions job wasn’t starting. In particular, it was hard to know if you were blocked by your concurrency limit as well as what was ahead of you in the queue. To help with this, we are pleased to share the new management experience for GitHub-hosted runners.
The new management experience enables you to see top-level summary information about your GitHub-hosted runners including:
- What the concurrency limits are for your organization
- How much of each runner type is being used at a given time
- The available runner labels that can be used in workflows
- The list of currently active jobs running on GitHub-hosted runners
From this new UI, you will be able to view and cancel any jobs blocking your more critical workflows from running across your organization.
Learn more
- For questions, visit the GitHub Actions community
- To see what’s next for Actions, visit our public roadmap
Tags:
Written by
Related posts
GitHub Copilot: Meet the new coding agent
Implementing features has never been easier: Just assign a task or issue to Copilot. It runs in the background with GitHub Actions and submits its work as a pull request.
Code. Create. Commit. Welcome to dev/core
The new GitHub Shop collection is here. We’re celebrating you.
GitHub Availability Report: April 2025
In April, we experienced three incidents that resulted in degraded performance across GitHub services.