CircleCI says the fix for its Oct 6 outage missed the log writes from deletions that were already scheduled for Oct 9. Three days later its database ran out of log space and went read-only.
This is from CircleCI’s postmortem for the Oct 9 incident, posted Oct 12, all times UTC. The report says the changes CircleCI made to resolve the Oct 6 outage “did not consider the additional log writes from scheduled deletions.” Temporal, its queueing system, is set to delete completed workflows and activities from its history 3 days after they complete, so the Oct 6 history came due on Oct 9.
The 34-second reel: the fix that missed scheduled deletes.
The timeline
From 08:00 on Oct 9, free space on the log volume fell from 0.8 TB to 0.1 TB by 10:10. At 11:15 it ran out and Postgres went read-only. Later that evening, after a pause in starting new work from 20:48 to 22:10, queued jobs resumed. Some had waited up to about 2 hours.
The deletions were not the whole story
The deletions explain the log volume running out, not all the delays. The report says the 15:15 delays came from deleted rows the database had not cleaned up, and that by 20:48 Postgres was “no longer bottlenecked on log writes.”
What CircleCI says it is changing
CircleCI says it split work across multiple Temporal instances, is changing when the deletions run, and is adding alerts on log archiving lag and log write rate.
Our reading
A delete schedule is a load schedule. The report itself says a busy day “returns as database load later in the week.” A bad day does not end when the incident closes. What runs three days after your worst day? Name one scheduled job you would check first.
What we did not verify
This is CircleCI’s own account in its postmortem, and we did not independently verify the timeline or the numbers. The postmortem for the Oct 9 incident was posted Oct 12, 2026, and the post-incident report for Oct 6 was posted Oct 7, 2026. All times in the report are UTC. The script was written with an AI model made by Anthropic, and the voiceover and visuals in the reel are AI-generated. Watch the reel on Threads or YouTube.
This post started as an Instagram post →
- https://www.instagram.com/reel/DeozNeHDkwR/
- https://www.threads.com/@dataeng.ai/post/Dew7cI4jpPZ
- https://www.youtube.com/shorts/j-83nIF7R5c
- https://status.circleci.com/incidents/6cfhhlr4rmm0
- https://discuss.circleci.com/t/post-incident-report-oct-6-2026-delays-in-pipelines-workflows-ui-data-and-notifications/54908
Numbers above trace to these sources. If one moved, tell us and we fix it.


Talk it through
Argue with us on Instagram.