When a GitHub Actions run is canceled before starting, inspect the workflow’s concurrency group. By default, one run can be active and one can wait in the same group. When another run arrives, it can replace the waiting run even when the active run is allowed to finish.


Pick the behavior your workflow needs


For pull-request checks, keeping the newest waiting run can reduce redundant work. Group by the workflow and the pull request or branch so unrelated work does not share a queue. If a newer commit should interrupt an active run, GitHub provides cancel-in-progress. Review workflows that deploy or write shared state before turning it on.


If every request matters


A release or delivery queue may need to retain more than one pending run. GitHub documents queue: max for groups that need multiple waiting runs. It cannot be combined with cancel-in-progress: true. Validate the workflow before relying on either setting.


How to confirm the cause


Compare the active, waiting and newly queued runs. Check that the group expression evaluates to the same key. Then trigger two harmless test runs and observe whether the earlier run finishes, waits, or is replaced.


GitHub documentation: https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency