GitHub Actions / GitHub Actions

GitHub Actions runner listener stops polling broker after Busy→Online transition on Windows

Fix GitHub Actions self-hosted runner on Windows where listener stops accepting new jobs after completing the first one Includes evidence for GitHub Actions troubleshooting demand.

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

Category: GitHub Actions
Error signature: Listener stops polling broker after first job's Busy→Online transition (runner v2.334.0, Windows, V2 flow)
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 21, 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

Listener stops polling broker after first job's Busy→Online transition (runner v2.334.0, Windows, V2 flow) is a GitHub Actions failure pattern reported for developers trying to fix github actions self-hosted runner on windows where listener stops accepting new jobs after completing the first one. 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#4444 — self-hosted runner on Windows v2.334.0 stops receiving jobs after first job transitions from Busy back to Online. Blocks entire CI/CD pipeline for teams relying on self-hosted runners. High urgency for production environments.

Common causes

GitHub issue actions/runner#4444 — self-hosted runner on Windows v2.334.0 stops receiving jobs after first job transitions from Busy back to Online. Blocks entire CI/CD pipeline for teams relying on self-hosted runners. High urgency for production environments.

Quick fixes

Confirm the exact error signature matches Listener stops polling broker after first job's Busy→Online transition (runner v2.334.0, Windows, V2 flow).
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 Listener stops polling broker after first job's Busy→Online transition (runner v2.334.0, Windows, V2 flow) 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 Listener stops polling broker after first job's Busy→Online transition (runner v2.334.0, Windows, V2 flow) mean in GitHub Actions?

Listener stops polling broker after first job's Busy→Online transition (runner v2.334.0, Windows, V2 flow) indicates the workflow described by "GitHub Actions runner listener stops polling broker after Busy→Online transition on Windows" failed in a GitHub Actions context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Listener stops polling broker after first job's Busy→Online transition (runner v2.334.0, Windows, V2 flow)?

Check whether this cause matches your environment: GitHub issue actions/runner#4444 — self-hosted runner on Windows v2.334.0 stops receiving jobs after first job transitions from Busy back to Online. Blocks entire CI/CD pipeline for teams relying on self-hosted runners. High urgency for production environments.

Is the Listener stops polling broker after first job's Busy→Online transition (runner v2.334.0, Windows, V2 flow) guidance source-backed?

The "GitHub Actions runner listener stops polling broker after Busy→Online transition on Windows" 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 Listener stops polling broker after first job's Busy→Online transition (runner v2.334.0, Windows, V2 flow)?

For "GitHub Actions runner listener stops polling broker after Busy→Online transition on Windows", 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 Listener stops polling broker after first job's Busy→Online transition (runner v2.334.0, Windows, V2 flow)?

For "GitHub Actions runner listener stops polling broker after Busy→Online transition on Windows", 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.