GitLab CI "interruptible" Not Cancelling Redundant Pipelines

By Kaveh Alemi·Latchkey

interruptible: true lets GitLab auto-cancel a running pipeline when a newer commit supersedes it. It stops working once a non-interruptible job has started, or when the project auto-cancel setting is disabled.

What this error means

Pushing a new commit does not cancel the older still-running pipeline, so redundant pipelines pile up and waste runner minutes - even though jobs are marked interruptible.

Pipeline behavior

# New commit pushed, but the previous pipeline keeps running.
test:
  interruptible: true
  script: make test
deploy:
  script: make deploy   # NOT interruptible -> locks the whole pipeline

Diagnose it: which rule matched, and on which runner?

GitLab evaluates rules: top to bottom and the first match wins, including one that sets when: never. A job that does not run, or runs when you did not expect it to, is nearly always matching an earlier rule than the one you are reading.

.gitlab-ci.yml

# validate the definition against the project
curl -s --header "PRIVATE-TOKEN: $TOKEN" \
  "https://gitlab.com/api/v4/projects/$CI_PROJECT_ID/ci/lint" \
  --data-urlencode "content=$(cat .gitlab-ci.yml)"

# what the job actually sees
script:
  - env | grep -E "^CI_(PIPELINE_SOURCE|COMMIT_REF_NAME|RUNNER)" | sort

Common causes

A non-interruptible job already started

Once any job without interruptible: true begins running, GitLab will no longer auto-cancel that pipeline - the whole pipeline becomes non-interruptible from that point.

Auto-cancel-redundant setting disabled

Auto-cancellation of redundant pipelines is a project CI/CD setting. If it is off, interruptible has no effect regardless of how jobs are marked.

How to fix it

Mark early jobs interruptible, gate deploys

Keep build/test interruptible and make irreversible jobs (deploys) manual or late so they do not start before cancellation can happen.

.gitlab-ci.yml

default:
  interruptible: true   # applies to all jobs by default

deploy:
  interruptible: false  # protect a real deployment from cancellation
  when: manual
  script: make deploy

Enable auto-cancel in project settings

Open Settings → CI/CD → General pipelines.
Enable "Auto-cancel redundant pipelines".
Confirm early jobs are interruptible so a newer commit cancels the older pipeline before deploy starts.

How to prevent it

Set interruptible: true via default: for build/test jobs.
Keep irreversible jobs (deploy/release) non-interruptible and gated.
Enable auto-cancel redundant pipelines at the project level.

Frequently asked questions

What causes GitLab CI "interruptible" not cancelling redundant Pipelines?

There are 2 common causes: a non-interruptible job already started and auto-cancel-redundant setting disabled. Once any job without interruptible: true begins running, GitLab will no longer auto-cancel that pipeline - the whole pipeline becomes non-interruptible from that point.

How do I fix GitLab CI "interruptible" not cancelling redundant Pipelines?

There are 2 fixes depending on which cause you have: mark early jobs interruptible, gate deploys and enable auto-cancel in project settings. Work through them in order, since the first is the most common.

What does GitLab CI "interruptible" not cancelling redundant Pipelines actually mean?

Pushing a new commit does not cancel the older still-running pipeline, so redundant pipelines pile up and waste runner minutes - even though jobs are marked interruptible.

How do I stop GitLab CI "interruptible" not cancelling redundant Pipelines happening again?

Set interruptible: true via default: for build/test jobs. The prevention section lists 3 changes that keep it from recurring.

References

GitHub Actions documentation