HTTP 429 Error in Journey Condition Activity

[LuisCardenas]

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')

[Mayank_Gandhi · Accepted solution]

@LuisCardenas we may want to check more detail on the error and discuss further, can you please log a support case and share the ticket number.

[SatheeskannaK]

@LuisCardenas http error code is related to the exceeding the maximum no. of requests that the event can handle. do you have any further information on how many requests are being posted to the event in a sec?

[Sukrity_Wadhwa]

Hi @LuisCardenas,

Were you able to resolve this query on your own or do you still need help here? Do let us know.

Thanks!

[Sukrity_Wadhwa]

Hi @LuisCardenas,

Since there hasn’t been any recent activity on this thread and as suggested by @Mayank_Gandhi, this use case should be addressed with the help of Adobe Support, so, we’ll be closing this question for now.
If you have any related questions or updates to share, please don’t hesitate to request to reopen this one or start a new thread. We’d be happy to take another look.
Thanks!