GitHub Actions Larger Runner Label Not Picked Up (runner groups)

By Daniel Zoghalchali·Latchkey

A job targeting a larger GitHub-hosted runner sits queued or fails to match because the runner group is not assigned to the repository, or the runs-on label does not match the runner you configured.

What this error means

A job requesting a custom larger-runner label never starts, or errors that no runner matches, even though the larger runner is configured at the org level.

Actions log

Waiting for a runner to pick up this job...
# runs-on: ubuntu-latest-8-cores, but the runner group is not
# assigned to this repository

Common causes

Runner group not granted to the repo

Larger runners live in a runner group. If that group is not assigned to the repository (or its visibility excludes it), the repo cannot use the runner.

Label name mismatch

The runs-on label must match the exact name configured for the larger runner. A typo or an old name matches nothing.

How to fix it

Grant the runner group and match the label

Assign the runner group to the repository in org settings and use the exact configured label.

.github/workflows/ci.yml

# org settings: add this repo to the runner group that owns the runner
jobs:
  build:
    runs-on: ubuntu-latest-8-cores   # exact configured label

Verify access and naming

In Settings > Actions > Runner groups, confirm the repository is allowed to use the group.
Copy the larger-runner label name exactly from the runner configuration.
Check billing/quota for larger runners has not been exhausted.

How to prevent it

Assign runner groups to the repositories that need larger runners.
Use the exact configured label name in runs-on.
Document larger-runner labels and their group assignments for the org.

Frequently asked questions

What causes "Larger runner label"?