Workflows stuck in "In progress" status

What to do

• Check whether you use Circle Workflows. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 3h 28m it lasted.

  Anything that failed between 2026-05-28 16:44 UTC and 2026-05-28 20:12 UTC may need a replay.

• Subscribe to Circle's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=circle works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Circle 5

1. investigatingMay 28, 2026, 4:44 PM UTC

   We are currently investigating this issue.

   provider

2. identifiedMay 28, 2026, 5:12 PM UTC

   The issue has been identified and a fix is being implemented.

   provider

3. monitoringMay 28, 2026, 6:46 PM UTC

   A fix has been implemented and we are monitoring the results.

   provider

4. resolvedMay 28, 2026, 8:12 PM UTC

   The issue has been fully resolved and all systems are operating normally. A detailed post-mortem report will be published here shortly. Thank you for your patience and cooperation.

   provider

5. postmortemJun 1, 2026, 3:06 PM UTC

   ## Delays in Asynchronous Actions and Workflows ‌ **Issue Summary** On May 28, 2026, we experienced an incident that caused delays in asynchronous actions and automated workflows. **Timeline \(UTC\)** * **11:29** – The issue began, causing delays in newly scheduled automated workflows. * **15:51** – Our engineering team identified the root cause of the scheduling interruption. * **16:42** – A fix was deployed, restoring normal operations to the background processing framework. * **18:45** – The resulting backlog of delayed tasks was completely cleared and normal service was confirmed. **Root Cause** A routine system update included a software dependency upgrade that unexpectedly conflicted with our background processing framework. This conflict prevented scheduled background jobs from moving into the active processing queue. As a result, automated workflows and other asynchronous actions were delayed, though no underlying data was lost or corrupted during this time. **Resolution** Upon investigating the anomaly in the scheduling queue, our engineering team determined that the recent dependency upgrade was responsible. We immediately reverted the update, which restored the flow of scheduled tasks. To resolve the issue as swiftly as possible, we temporarily scaled up our infrastructure's processing capacity to rapidly clear the backlog of delayed actions. **Preventative Measures** To prevent this type of issue from occurring in the future, we are planning on implementing the following improvements: * **Enhanced Alerting:** We are deploying strict, automated alerts specifically designed to detect anomalies in scheduled task queues, drastically reducing our time to detection. * **Upgraded Telemetry:** We are adding granular, time-series visualizations to our monitoring systems to better track the exact states of background jobs \(scheduled, enqueued, and processed\) in real time. We sincerely apologize for any disruption this may have caused to your operations. The issue was fully mitigated, and all backlogged tasks have been successfully processed.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.