Incorrect Journey Filter Processing

Incident Report for Iterable

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

Posted Jul 11, 2022 - 09:00 PDT