---
title: "Comment by OneLifeVibe on \"A Queued GitHub Actions Job Is Waiting on One of Five Things\" | Hashnode"
description: "This is a useful diagnostic frame. The point about measuring created_at against started_at stood out, because the Actions UI hides the wait itself and makes a q"
url: "https://hashnode.com/posts/a-queued-github-actions-job-is-waiting-on-one-of-five-things/6aff17d848e5984fd528af8c/comment/6aff238f4efb27599ea3a09d"
---

[Discussion](https://hashnode.com/posts/a-queued-github-actions-job-is-waiting-on-one-of-five-things/6aff17d848e5984fd528af8c)

Comment [A Queued GitHub Actions Job Is Waiting on One of Five Things](https://hashnode.com/posts/a-queued-github-actions-job-is-waiting-on-one-of-five-things/6aff17d848e5984fd528af8c)

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[1d ago](https://hashnode.com/posts/a-queued-github-actions-job-is-waiting-on-one-of-five-things/6aff17d848e5984fd528af8c/comment/6aff238f4efb27599ea3a09d)

This is a useful diagnostic frame. The point about measuring created\_at against started\_at stood out, because the Actions UI hides the wait itself and makes a queue look like slow execution. I also liked the warning about a concurrency group with no branch in it, since that failure looks exactly like a capacity shortage. The macOS limit of five concurrent jobs is another one that catches teams by surprise when an iOS build suddenly sits queued for many minutes.
