GitHub Actions Self-Hosted Runner busy State Desync Causes Auto-Scaler to Kill Running Jobs

What this error means

REST API GET /repos/{owner}/{repo}/actions/runners/{runner_id} returns busy: false while runner is actively executing a job is a GitHub Actions failure pattern reported for developers trying to fix github actions self-hosted runner being terminated mid-job by auto-scaler due to incorrect busy state. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue actions/runner#4422 (May 14, 2026): Non-ephemeral self-hosted runners on AWS show busy:false in REST API while actively executing jobs. Auto-scaling Lambda polls REST API, sees idle, terminates instance, killing the running job. Broker knows runner is busy but REST API doesn’t. Category: GitHub Actions (CI/CD infrastructure).

Common causes

• GitHub issue actions/runner#4422 (May 14, 2026): Non-ephemeral self-hosted runners on AWS show busy:false in REST API while actively executing jobs. Auto-scaling Lambda polls REST API, sees idle, terminates instance, killing the running job. Broker knows runner is busy but REST API doesn’t. Category: GitHub Actions (CI/CD infrastructure).

Quick fixes

1. Confirm the exact error signature matches REST API GET /repos/{owner}/{repo}/actions/runners/{runner_id} returns busy: false while runner is actively executing a job.
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 actions/runner#4422 (May 14, 2026): Non-ephemeral self-hosted runners on AWS show busy:false in REST API while actively executing jobs. Auto-scaling Lambda polls REST API, sees idle, terminates instance, killing the running job. Broker knows runner is busy but REST API doesn’t. Category: GitHub Actions (CI/CD infrastructure).

Related errors

• GitHub Actions

FAQ

What should I check first?

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