Iterable: Incorrect Journey Filter Processing
Timeline of updates
- resolved
After receiving reports of incorrect journey filter processing beginning around 9 am PDT our engineering team identified a bug with journey filter nodes. This bug caused users to incorrectly process down the "NO" path within fields match filters. We deployed a fix that went live at approximately 12pm PDT and has seen no further instances of incorrect filtering. If you have any questions please reach out to your account manager or email 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 2022-07-11 16:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Incorrect Journey Filter Processing
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/cczqzrdfyhtd
Iterable profileRecent Iterable incidentsAll outages on July 11, 2022Iterable in July 2022MarkdownJSON