Seven causes of GitHub Actions jobs stuck in Queued, and how to fix each
Jobs that sit in Queued for more than a minute or two are usually held up by one of seven specific causes, and adding runners only resolves some of them. The article explains that the GitHub API, not the Actions UI, exposes queue time through each job's created_at and started_at timestamps, and provides a command to list the longest waits across recent runs. It notes that a median wait measured in minutes signals a problem, while a healthy example showed a median of 13 seconds. The main culprit discussed is GitHub-hosted runner concurrency caps, which differ by plan, with macOS jobs limited to five concurrent slots on Free, Pro and Team plans. Suggested remedies include cancelling superseded runs, trimming test matrices, merging very short jobs, requesting higher limits from GitHub Support, and moving heavy jobs to self-hosted or third-party runners.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in