Is there a way to debug what went wrong in Journey custom action? | Community
Skip to main content
arpan-garg
Community Advisor
arpan-gargCommunity Advisor
Community Advisor
March 12, 2024
Solved

Is there a way to debug what went wrong in Journey custom action?

  • March 12, 2024
  • 1 reply
  • 1937 views

Hi,

 

I created a journey and included a custom action (which should call an API and get a response). When i am running my journey my custom action always goes in timeout step and ends the journey. However when i hit the same API via postman i get result immediately.

 

This is what i see in test mode 

 

Is there a way to debug it? Can i somehow see what call is being made by custom action ? 

Maybe the system which i am calling needs to whitelist AJO IP range?

 

Any inputs will be appreciated.

 

Thanks,

Arpan

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SatheeskannaK

@arpan-garg 

The lack of visibility into the cause of failure is a common issue when dealing with custom actions. It is important to verify whether custom actions are compatible with other endpoints. One way to test this is by trying it with a public endpoint and observing the results. If the custom action successfully works with the public endpoint, it would be beneficial to provide additional details about the custom action payload and the specific journey you are currently working on.

1 reply

Mohan_Dugganab
Adobe Employee
Mohan_DugganabAdobe Employee
Adobe Employee
March 12, 2024

Can you increase the timeout to 30 seconds in the journey properties and see if its still the same case ?

 

 

arpan-garg
Community Advisor
arpan-gargCommunity AdvisorAuthor
Community Advisor
March 12, 2024

Hi @mohan_dugganab - Timeout I have set already to 30 seconds, and I have the same issue 

SatheeskannaK
Community Advisor
SatheeskannaKCommunity AdvisorAccepted solution
Community Advisor
March 12, 2024

@arpan-garg 

The lack of visibility into the cause of failure is a common issue when dealing with custom actions. It is important to verify whether custom actions are compatible with other endpoints. One way to test this is by trying it with a public endpoint and observing the results. If the custom action successfully works with the public endpoint, it would be beneficial to provide additional details about the custom action payload and the specific journey you are currently working on.

Thanks, Sathees
Terms & ConditionsAccessibility statement

Loading footer...