GitHub Actions / GitHub Actions
GitHub Actions Self-Hosted Runner — REST API Reports Idle While Job Running
Fix GitHub Actions self-hosted runner showing busy:false while actually executing jobs Includes evidence for GitHub Actions troubleshooting demand.
- Category
- GitHub Actions
- Error signature
/runners REST API reports busy: false for self-hosted runner actively executing job- Quick fix
- Compare the failing environment with a known working setup, then change one configuration value at a time.
- Updated
What this error means
/runners REST API reports busy: false for self-hosted runner actively executing job is a GitHub Actions failure pattern reported for developers trying to fix github actions self-hosted runner showing busy:false while actually executing jobs. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
Self-hosted runner REST API reports busy:false while the runner is actively executing a job. Broker says busy, REST API says idle. Causes duplicate job assignments.
Common causes
- GitHub Actions /runners REST API incorrectly reports busy:false for self-hosted runners that are actively running jobs, causing scheduling issues and resource allocation problems in self-hosted runner pools
- Self-hosted runner REST API reports busy:false while the runner is actively executing a job. Broker says busy, REST API says idle. Causes duplicate job assignments.
Quick fixes
- Confirm the exact error signature matches
/runners REST API reports busy: false for self-hosted runner actively executing job. - Check the GitHub Actions account, local tool state, and provider configuration involved in the failing workflow.
- Compare the failing environment with a known working setup, then change one configuration value at a time.
Platform/tool-specific checks
- Verify the command, editor, extension, or API client that produced the error.
- Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
- Avoid deleting credentials, local model data, or project settings until the failing scope is clear.
Step-by-step troubleshooting
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- Keep the working fix documented for the team or deployment environment.
How to prevent it
- Keep provider/tool configuration documented.
- Record non-secret diagnostics such as tool version, provider name, model name, and command path.
- Add a lightweight check before CI or production workflows depend on the tool.
Sources checked
Evidence note: Self-hosted runner REST API reports busy:false while the runner is actively executing a job. Broker says busy, REST API says idle. Causes duplicate job assignments.
Related errors
- GitHub Actions runner stuck
- GitHub Actions self-hosted runner busy
- GitHub Actions runner not picking up jobs
FAQ
What should I check first?
Start with the exact /runners REST API reports busy: false for self-hosted runner actively executing job text and the smallest action that reproduces it.
Can I ignore this error?
No. Treat it as a failed GitHub Actions workflow until the root cause is understood.
Is this guaranteed to have one fix?
No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.
How do I know the fix worked?
Rerun the same command, editor action, or request. The fix is working when that action completes without /runners REST API reports busy: false for self-hosted runner actively executing job.