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.

Source-backed Last updated May 15, 2026 1 source Needs local verification

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: May 15, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for GitHub Actions, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

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.

Diagnostic flow for this page

Match /runners REST API reports busy: false for self-hosted runner actively executing job exactly before applying the quick fix.
Compare the failing environment with GitHub Actions versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does /runners REST API reports busy: false for self-hosted runner actively executing job mean in GitHub Actions?

/runners REST API reports busy: false for self-hosted runner actively executing job indicates the workflow described by "GitHub Actions Self-Hosted Runner — REST API Reports Idle While Job Running" failed in a GitHub Actions context. Start by confirming the exact signature and the component that emitted it.

What should I check first for /runners REST API reports busy: false for self-hosted runner actively executing job?

Check whether this cause matches your environment: 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

Is the /runners REST API reports busy: false for self-hosted runner actively executing job guidance source-backed?

The "GitHub Actions Self-Hosted Runner — REST API Reports Idle While Job Running" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for /runners REST API reports busy: false for self-hosted runner actively executing job?

For "GitHub Actions Self-Hosted Runner — REST API Reports Idle While Job Running", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging /runners REST API reports busy: false for self-hosted runner actively executing job?

For "GitHub Actions Self-Hosted Runner — REST API Reports Idle While Job Running", collect the failing GitHub Actions command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.