Changes / GitLab / CI/CD pipelines remain stuck in running status
GitLab: Major incident: CI/CD pipelines remain stuck in running status
Summary
Summary pending. The diff below shows exactly what changed.
Incident page: full timeline of updates →
What changed
Before: not present
After: CI/CD pipelines remain stuck in running status
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-03-06 17:48 UTC
Before: not present
After: 2026-03-06 20:31 UTC
Before: not present
After: CI/CD
Before: not present
After: Pipelines affected by a previous incident on 3/5 continue to be stuck in Running status. We are working on a process to identify and safely correct these stuck pipelines, and will update this notice once that remediation is in place. Follow https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21462 for details.
Before: not present
After: After consideration, we have decided not to automatically change previously stuck pipelines. Doing so could cause unsafe or stale state changes, for example around deployments and environments.
Before: not present
After: If a pipeline still appears stuck, please cancel and retry the affected job or pipeline. Protections deployed during this incident will prevent this in new pipelines. See https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21462 for complete details.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: CI/CD pipelines remain stuck in running status (this change) | Major incident |