Question

An enterprise administrator notices that CI jobs in a busy organization are stuck in the 'Queued' state for 15-20 minutes before starting on self-hosted runners. The runner group has 4 registered self-hosted runners, all of which show as 'Idle' in the runner settings UI, yet jobs are not being picked up. Job labels in the workflow specify 'runs-on: [self-hosted, linux, gpu]'. What is the MOST likely cause of the queuing delay?

Accepted Answer

The registered runners do not carry all of the labels (specifically the 'gpu' label) requested by the workflow, so no runner matches the job's label set.

Answer

The organization has exceeded its GitHub-hosted runner concurrency limit and must wait for capacity.

Answer

The runner group's IP allow list is blocking inbound connections from GitHub, preventing job assignment.

Answer

Encrypted organization secrets referenced by the workflow have not been approved, which holds the jobs in the queue.