# GitLab: CI/CD pipelines remain stuck in running status

- Impact (vendor’s label): major
- Status: resolved
- Started: 2026-03-06 17:48 UTC · Resolved: 2026-03-06 20:31 UTC · Duration: 2.7 h
- Updates: 3 · Affected components: CI/CD
- [Vendor status page: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/69ab136e57b5f1057a500446](https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/69ab136e57b5f1057a500446)
- [Company: GitLab](https://rewindex.com/company/gitlab.md)

## Timeline of updates

- **identified** 2026-03-06 17:48 UTC: 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.
- **identified** 2026-03-06 20:30 UTC: 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.
- **resolved** 2026-03-06 20:31 UTC: 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.

## Rewindex changes for this incident

- 2026-03-06 17:48 UTC: [Major incident: CI/CD pipelines remain stuck in running status](https://rewindex.com/change/i6483e0f44591e9.md)


---
Canonical: https://rewindex.com/company/gitlab/incidents/69ab136e57b5f1057a500446 · Markdown: https://rewindex.com/company/gitlab/incidents/69ab136e57b5f1057a500446.md · JSON: https://rewindex.com/api/v1/companies/gitlab/incidents/69ab136e57b5f1057a500446 · Generated 2026-10-18T10:26:14.377Z