Iterable: Workflow memory issues
Timeline of updates
- resolved
We continue to see no new impact related to the memory issues earlier in the day. Our engineers have uncovered one side effect in which in certain limited cases it appears as though users are stuck in a journey. We have confirmed that in these cases it is an issue with the UI, and that the users did in fact progress. We have initiated efforts to remediate the incorrect counts of stuck users, and we expect that process to be completed tomorrow (Friday). For now, we will go ahead and close out this incident. Thank you for your patience - please reach out to us at support@iterable.com if you have any further questions.
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-12-01 16:24 UTC, resolved after 11 h, 1 update(s).
- Title
- Workflow memory issues
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/gpqvrfcpfpfd
Iterable profileRecent Iterable incidentsAll outages on December 1, 2022Iterable in December 2022MarkdownJSON