Iterable: Delayed performance for workflow processing
Timeline of updates
- resolved
The fix deployed by our engineering team has resolved the issue and workflow processing has fully recovered. The impact window began for a small subset of customers at approximately 8 AM PST and continued throughout the day until the fix was deployed and we were fully recovered by 2 PM PST. If you have any additional questions please contact your account manager or email support at support@iterable.com A customer facing RCA will be made available upon request.
From Iterable’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.iterable.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Iterable, started 2022-02-10 19:58 UTC, resolved after 4.2 h, 1 update(s).
- Title
- Delayed performance for workflow processing
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/9svr6dnnhrnm
Iterable profileRecent Iterable incidentsAll outages on February 10, 2022Iterable in February 2022MarkdownJSON