# CI/CD Pipelines stuck in running status (Severity 2) **Problem**: CI/CD pipeline and job statuses did not transition to completed. Jobs were stuck in 'Created' status and pipelines remained in 'Running' status even after all jobs finished. **Impact**: About 3,500 pipelines across many customer projects became stuck in 'running' status and could not complete. Most affected projects had only one stuck pipeline, with the highest being 15. Customers could not complete these CI/CD pipelines, blocking deployments and feature flag changes until the pipeline was manually retried. **Causes**: Jobs deferred by the concurrency limit were never resumed, causing pipelines to stay in the running state. Disabling the concurrency limiter for PipelineProcessWorker prevented new pipelines from getting stuck. The underlying bug matches a previously reported issue (https://gitlab.com/gitlab-org/gitlab/-/work_items/582085). **Response strategy**: We disabled the concurrency limiter for PipelineProcessWorker, which stopped new pipelines from getting stuck. Customers can cancel and retry affected pipelines as a workaround. We decided not to process stuck pipelines automatically to avoid unsafe or stale state changes. A long-term fix is being tracked in GitLab issue https://gitlab.com/gitlab-org/gitlab/-/work_items/582085. _This ticket was created to track_ [_INC-8087_](https://app.incident.io/gitlab/incidents/8087)_, by_ [_incident.io_](https://app.incident.io) 🔥