Incidentsby GlyphSome jobs were not triggered and will need to be manually retried
Nov 25, 16:10 UTCNov 25, 16:10 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
CircleCI, 90 days
24 incidents
Affected
Not listed by the vendor.
Final update
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).
Timeline
- Resolved · Nov 25, 16:10 UTC
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).
More from CircleCI
Full historyIncreased wait time for Machine and Remote Docker jobsFrom 13:55 to 15:07 UTC on November 3, customers running Linux machine jobs and Remote Docker saw increased wait times for their jobs to start, and the delays were longest from 14:16 to 14:41.lasted 54mPostmortemDelays for gen2 dedicated IP range jobslasted 1h 3mIncreased Docker gen2 wait timeslasted 1h 24mIncreased wait times for macOS jobs on m4pro.largelasted 2h 16mDelays starting macOS jobs that use Xcode 26.6.0lasted 1h 13mDelay in data appearing in UI and APIlasted 14h 36m