CircleCI: Some builds inadvertently failed with "no configuration was found" errors
Timeline of updates
- resolved
Between 10:18 UTC and 17:54 UTC, a small number of workflows may have inadvertently encountered a build error "No configuration was found in your project." despite the repository containing a valid .circleci/config.yml. We have reverted a recent change and these errors should no longer be encountered. Any impacted users will need to push a fresh commit to trigger a successful build.
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 2020-10-23 10:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Some builds inadvertently failed with "no configuration was found" errors
- Vendor
- CircleCI
- Date
- URL
- https://rewindex.com/company/circleci/incidents/l8d82y3hwj2s
CircleCI profileRecent CircleCI incidentsAll outages on October 23, 2020CircleCI in October 2020MarkdownJSON