3

When a Custom Activity in Journey Builder tries to POST to the app's external API endpoint and gets a 400 error, what happens to the subscriber's flow through the journey?

  • Does SFMC retry the API call a certain number of times? Indefinitely?
  • Does the subscriber get ejected from the Journey?
  • Do they get permanently stuck in the custom Journey Builder Activity?
  • Or is the error simply logged and they move onto the next step? And if so, where is it logged?

To be clear, this is asking about the call SFMC makes to the host of the app (SFMC->Heroku) NOT the call the app makes to SFMC (Heroku->SFMC).

2
  • Does SFMC retry the API call a certain number of times? Indefinitely? Answer: No, there's no retry. There's only a retry if your execute request times out, read further on: https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-app-development.meta/mc-app-development/custom-activity-config.htm
  • Does the subscriber get ejected from the Journey? Answer: I haven't tested this recently but I think so, this will be an easy test to perform.
  • Do they get permanently stuck in the custom Journey Builder Activity? Answer: Similar to above no, they just get rejected.
  • Or is the error simply logged and they move onto the next step? And if so, where is it logged? Answer: It doesn't move to the next step, the only way it will move to the next step is if your activity has branches and you return an HTTP 200 with the corresponding branch key.
1
  • "and you return an HTTP 200 with the corresponding branch key"
    – Will
    Aug 11 '21 at 15:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.