HTTP 429 Error in Journey Condition Activity
Hi all,
We have a live journey which is triggered by a unitary event, and inmeditaley after is followed by a condition activity that checks a couple of profile attributes (to serve as a filter) to only allow Friends&Family profiles to continue the journey. The issue here is that we're getting HTTP 429 error in the condition, resulting in a big number of profiles being discarded.
Do you have any suggestion/explanation on how to resolve this?
Here's the condition used (fictional):
(#{ExperiencePlatform.ProfileFieldGroup.profile.customerId} == 'Test-xxx') or
(#{ExperiencePlatform.ProfileFieldGroup.profile.customerId} == 'Test-yyy')