Decision splits evaluating contacts incorrectly due to caching issues for similar criteria.
Last updated 2019-10-30 ·Reference W-6592986 ·Reported By 3 users
Journey Builder caches decision split criteria selectors for maximum performance. However, due to an issue, filters using different data types are cached using the same cache key. As a result, the decision split fails when evaluating the decision split filter.
-Create a Journey with multiple decision splits
-Create first decision split filter as a numeric Attribute compared with a fixed value
-Create second decision split as an Attribute to Attribute comparison, using the same Attribute as previous step
Ensure that each decision split is distinct enough so that they are evaluated separately.
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.