GitHub Actions REST API reports busy:false for self-hosted runner actively executing job, auto-scaler kills it

What this error means

GET /repos/{owner}/{repo}/actions/runners/{id} returns busy:false while runner is actively executing a job with valid lease is a GitHub Actions failure pattern reported for developers trying to fix github actions self-hosted runner rest api returning stale busy state, causing auto-scaler to terminate running jobs. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #4422 on actions/runner (2026-05-14): Self-hosted runners on AWS show state desync between broker (reports busy) and REST API (reports idle). Auto-scaling Lambda polls REST API, sees busy:false, terminates instance mid-job. Occurred twice in 10 minutes on independent runners. Category: GitHub Actions (CI/CD pipeline failure for paid teams).

Common causes

• GitHub issue #4422 on actions/runner (2026-05-14): Self-hosted runners on AWS show state desync between broker (reports busy) and REST API (reports idle). Auto-scaling Lambda polls REST API, sees busy:false, terminates instance mid-job. Occurred twice in 10 minutes on independent runners. Category: GitHub Actions (CI/CD pipeline failure for paid teams).

Quick fixes

1. Confirm the exact error signature matches GET /repos/{owner}/{repo}/actions/runners/{id} returns busy:false while runner is actively executing a job with valid lease.
2. Check the GitHub Actions account, local tool state, and provider configuration involved in the failing workflow.
3. 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

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. 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

• https://github.com/actions/runner/issues/4422

Evidence note: GitHub issue #4422 on actions/runner (2026-05-14): Self-hosted runners on AWS show state desync between broker (reports busy) and REST API (reports idle). Auto-scaling Lambda polls REST API, sees busy:false, terminates instance mid-job. Occurred twice in 10 minutes on independent runners. Category: GitHub Actions (CI/CD pipeline failure for paid teams).

Related errors

• GitHub Actions

FAQ

What should I check first?

Start with the exact GET /repos/{owner}/{repo}/actions/runners/{id} returns busy:false while runner is actively executing a job with valid lease 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 GET /repos/{owner}/{repo}/actions/runners/{id} returns busy:false while runner is actively executing a job with valid lease.