CircleCI: Job failed due to excessive concurrency limits
Timeline of updates
- resolved
Between 14:00 and 14:15 UTC a small number of jobs were rejected with the message “Job failed due to excessive concurrency limits”. Please re-run any jobs that failed with this message. If you continue to see the error, please contact CircleCI Support
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 2023-05-31 16:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Job failed due to excessive concurrency limits
- Vendor
- CircleCI
- Date
- URL
- https://rewindex.com/company/circleci/incidents/pn6jbtf1cpm4
CircleCI profileRecent CircleCI incidentsAll outages on May 31, 2023CircleCI in May 2023MarkdownJSON