CircleCI: Some jobs were not triggered and will need to be manually retried
Timeline of updates
- resolved
There was a short issue from 16:10 UTC to 16:13 UTC which meant that we did not successfully trigger some jobs. If you expected a job to run which did not within the last 30 minutes you should attempt to run the job manually or attempt to trigger the job again. (For example, by pushing to your repository).
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: none) posted by CircleCI, started 2025-11-25 16:10 UTC, resolved after 0 min, 1 update(s).
- Title
- Some jobs were not triggered and will need to be manually retried
- Vendor
- CircleCI
- Date
- URL
- https://rewindex.com/company/circleci/incidents/ptfypc6vygft
CircleCI profileRecent CircleCI incidentsAll outages on November 25, 2025CircleCI in November 2025MarkdownJSON