Ziflow incident
Delays creating proofs from intake forms and workflows
Ziflow experienced a minor incident on October 21, 2026 affecting Proof Processing and Zibots, lasting 4h 41m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 21, 2026, 04:59 PM UTC
We've identified the cause of delays affecting proof creation from intake forms and automated workflows. A backlog of queued requests is being processed, and proofs will be created as it clears; no action is needed from users and submissions do not need to be resent. Next update in approximately 60 minutes.
- identified Oct 21, 2026, 06:09 PM UTC
We’re continuing to work through delayed proof creation from intake forms and automated workflows. Part of the backlog has been cleared, and our team is actively addressing the remaining delayed requests. Submissions do not need to be resent; proofs will be created once processing completes. Next update in approximately 60 minutes, or sooner if there is a material change.
- monitoring Oct 21, 2026, 07:19 PM UTC
Our team continues to work through the backlog affecting proof creation from intake forms and automated workflows. Queues are steadily clearing, and new submissions are being processed in order as the backlog clears, so some delays will continue in the meantime. Submissions do not need to be resent. Next update in approximately 60 minutes.
- monitoring Oct 21, 2026, 08:17 PM UTC
Our team is deploying a fix to increase processing speed for the queued intake form requests, and proofs will be created as the backlog clears. Submissions do not need to be resent. Next update in approximately 60 minutes.
- resolved Oct 21, 2026, 09:41 PM UTC
This incident has been resolved. The issue was caused by a processing backlog that delayed proof creation from intake form submissions. A fix has been deployed, all delayed requests have been processed, and all affected systems are now operational.