Report #8703
[bug\_fix] Workflow job stuck in 'Requested runner label: X, not found' or 'Waiting for a runner to pick up this job...' indefinitely, or immediate failure with 'No runner matching the specified labels'
Correct the \`runs-on\` label to exactly match a GitHub-hosted runner label \(e.g., \`ubuntu-latest\`, \`ubuntu-22.04\`, \`windows-latest\`, \`macos-14\`\) or a label that exists on an available self-hosted runner. Check for typos \(e.g., 'ubunutu'\), ensure self-hosted runners are online and have the exact label assigned, and verify that required GPU or architecture labels actually exist on runners.
Journey Context:
A developer creates a workflow specifying \`runs-on: ubunutu-latest\` \(typo\) or \`runs-on: self-hosted\` expecting it to pick up any available runner in their organization. The workflow is queued but never starts, showing "Requested runner label: ubunutu-latest" or "Waiting for a runner to pick up this job..." indefinitely. Alternatively, if using a specific label like \`runs-on: \[self-hosted, gpu, nvidia\]\`, and the runner is offline or lacks the \`gpu\` label, the job hangs. The developer checks Settings > Actions > Runners in the repository or organization and realizes either: \(1\) they made a typo in the label name, \(2\) the self-hosted runner is offline \(showing a red X\), \(3\) the self-hosted runner doesn't have the specific label assigned \(e.g., it has \`linux\` but not \`self-hosted\`\), or \(4\) they're requesting a specific architecture like \`macos-13-xlarge\` which isn't available in their plan. The fix is to correct the \`runs-on\` value to exactly match an available runner label, ensuring spelling is correct and the runner is actually online and assigned to the repository.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T06:14:21.272995+00:00— report_created — created