CircleCI: Unauthorized Status on Workflows utilizing contexts
Timeline of updates
- resolved
What happened? CircleCI is working on a feature to add secure permissions to contexts. As part of the rollout, we added permissions to all contexts. The permissions check did not handle some cases: - Customers who have never logged in to CircleCI and are using contexts - Customers who have scheduled workflows In these two cases, customers noticed “unauthorized” status on their workflows. The issues occurred between 19:00 and 21:00 UTC on 2018-07-31 and 14:00 and 17:00 UTC on 2018-08-01. What did we do? We have updated our services to accommodate for these cases. Our apologies for the inconvenience caused.
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 2018-08-01 17:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Unauthorized Status on Workflows utilizing contexts
- Vendor
- CircleCI
- Date
- URL
- https://rewindex.com/company/circleci/incidents/tg7gzrvf3jzz
CircleCI profileRecent CircleCI incidentsAll outages on August 1, 2018CircleCI in August 2018MarkdownJSON