hosted-runner page in org is buggy

[ReenigneArcher]

Why are you starting this discussion?

Bug

What GitHub Actions topic or product is this about?

Metrics & Insights

Discussion Details

The hosted-runner page under the org settings is pretty buggy.

1. currently I am consuming all of my available runners, but 0 is shown for each OS type
2. The labels are outdated, many of these are no longer available, and many of the new ones are not shown

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

[jiscop85]

textThe GitHub-hosted runners metrics page (Organization settings → Actions → Runners → Metrics & Insights) currently has a few noticeable bugs:

• Usage is displayed as 0 minutes/jobs for all OS types (Ubuntu, Windows, macOS), even though my organization is actively consuming all available included minutes and runners are in use.
• The list of available runner labels is severely outdated:
  • Many labels that are no longer offered by GitHub are still shown.
  • Several newer labels (e.g., newer Ubuntu versions, Windows Server 2022 variants, or macOS 14) are completely missing.

This makes it impossible to accurately monitor current consumption or plan for larger runners.

Attached is a screenshot demonstrating the issue (0 usage shown despite full consumption).

Has anyone else encountered this? Is this a known issue, and is there an estimated time for a fix or a workaround to view accurate metrics in the meantime?

Thanks!

[ReenigneArcher]

It's not copilot related so they don't care to fix it.

[AhmedSAAhmed]

You are absolutely right this is a known issue with that specific settings view! Both of the bugs you are seeing are due to how that legacy UI component pulls and displays data.

Here is what's happening under the hood:

The 20/20 vs 0/0/0 metric discrepancy: The overall "All jobs usage" counter updates almost instantly when your organization hits its concurrency limit (which is 20 for your current plan). However, the telemetry that feeds the specific OS breakdown (Linux/Windows/macOS) is often delayed or fails to sync properly during periods of high job churn. It's a UI reporting lag, not an actual runner allocation failure.

The outdated labels: The runner labels shown on this specific settings page are essentially hardcoded static text. GitHub hasn't updated this specific view to reflect recent runner deprecations (like macos-11 and windows-2019) or the rollout of newer standard images.

The Workaround:
To get an accurate, real-time look at what is actually consuming your 20 concurrency slots, it's best to avoid this page. Instead, you can:

Check the Insights -> Actions tab at the organization level for better metric reporting.

Use the GitHub CLI (gh run list) or the Actions REST API to see exactly which workflows are currently in an in_progress state across your repositories.

[ReenigneArcher]

Thanks AI

Or Microsoft could actually fix the bug...

[AhmedSAAhmed]

This is the only workaround i came across