Iterable: Some workflows failed to trigger
Timeline of updates
- resolved
Our engineers were able to confirm that approximately between 4pm on 11/18 and 4am on 11/19 a small percentage of users that should have been triggered into workflows did not get triggered. Our customer success team is reaching out today to customers who were most impacted by this issue to determine how to handle those users. If you need additional info or help, don't hesitate to connect with us at support@iterable.com
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: none) posted by Iterable, started 2020-11-19 14:31 UTC, resolved after 32 h, 1 update(s).
- Title
- Some workflows failed to trigger
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/d0tvgnlcfbh2
Iterable profileRecent Iterable incidentsAll outages on November 19, 2020Iterable in November 2020MarkdownJSON