Troubleshooting
Runners page is empty
No runners listed — usually this is the expected state for orgs without self-hosted runners.
This is usually normal
If your organization uses only GitHub-hosted runners, the self-hosted runner sections show an empty state — GitHub does not expose its hosted fleet per runner, so there is simply nothing to list. This is expected, not an error.
If you do have self-hosted runners
- Org-level vs repo-level — runners registered at repository level appear under their repo; org-level groups appear for the organization.
- Permission — reading org runners requires the app permission; check GitHub for a pending permission request.
- Sync — runner data refreshes through the GitHub API; if the rest of the dashboard also looks stale, see no data after install.
Queue metrics look high
Queue wait time is measured for your jobs. High values with an empty self-hosted list mean GitHub-hosted capacity is the bottleneck — check the queued jobs tab and schedule contention for burst causes.