CircleCI "Build was canceled" - Why Jobs Get Canceled
The job did not fail on its own - CircleCI canceled it. The usual reasons are auto-cancel of a superseded pipeline, a manual cancel, or a fail-fast workflow stopping the rest after another job failed.
What this error means
A job ends with a grey "Canceled" status and "Build was canceled", with no test or build error of its own. Often it happens right after a newer commit is pushed to the same branch.
Build was canceledCommon causes
Auto-cancel of redundant pipelines
With "Auto-cancel redundant workflows" enabled, pushing a new commit to a branch cancels the still-running older pipeline for that branch. The cancel is expected, not a failure.
A manual cancel
Someone clicked cancel in the UI or via the API, stopping the workflow.
Fail-fast stopping sibling jobs
When a required upstream job fails, dependent jobs are canceled because their prerequisite never succeeded.
How to fix it
Confirm whether it was auto-cancel
- Check if a newer commit on the same branch started a fresh pipeline at the same time.
- Look at Project Settings → Advanced for "Auto-cancel redundant workflows".
- If the cancel was intentional (superseded), no action is needed.
Disable auto-cancel where you need every commit built
For release or deploy branches where each commit must run to completion, turn auto-cancel off (or scope it to PR branches).
Fix the upstream failure for fail-fast cancels
If sibling jobs were canceled because a required job failed, the real fix is the upstream failure - the cancel is a symptom.
How to prevent it
- Keep auto-cancel on for PR branches to save minutes, off for deploy branches.
- Treat canceled dependents as a pointer to the failed upstream job.
- Communicate manual cancels so they are not mistaken for flakes.