Why GitHub Actions cancels runs with 'higher priority waiting request' and how to set concurrency
The message 'Canceling since a higher priority waiting request exists' means a concurrency group is functioning as intended, not that something failed. GitHub permits only one running and one pending run per group, so a newer pending run displaces the older one. Cancellation is usually desirable for CI but harmful for deployments, where killing an in-flight run can leave infrastructure half-updated. The recommended fix for deploy workflows is to key the concurrency group to the target environment and set cancel-in-progress to false, letting stale queued commits be skipped rather than interrupting active ones. A short comparison table maps group keys and cancellation settings to CI, deploys, cron jobs, and preview builds.
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