CircleCI: Jobs stuck in running state
Timeline of updates
- resolved
Between 16:20 and 16:32 UTC, job triggering and workflow starts experienced disruptions across all resource classes due to memory pressure on our internal job distributor systems. We identified the issue and scaled our infrastructure to handle the load. Services returned to normal operation at 16:32 UTC. What was impacted: Job triggering and workflow starts were disrupted for 12 minutes. Some workflows and jobs appeared stuck in a running state during this window. Resolution: Our systems are now operating normally with additional capacity in place to prevent similar disruptions. If you had workflows or jobs that were stuck during this window, please manually rerun them. The incident is now resolved and we will be conducting a thorough review to understand what triggered the memory pressure and identify any additional preventive measures
From CircleCI’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.circleci.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by CircleCI, started 2025-12-03 16:53 UTC, resolved after 1.3 h, 1 update(s).
- Title
- Jobs stuck in running state
- Vendor
- CircleCI
- Date
- URL
- https://rewindex.com/company/circleci/incidents/kvzp8x242n34
CircleCI profileRecent CircleCI incidentsAll outages on December 3, 2025CircleCI in December 2025MarkdownJSON