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

Question

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

SatheeskannaK · Accepted Answer

@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.

Mohan_Dugganab · Answer

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

가입하기

소셜 로그인

커뮤니티에 로그인

소셜 로그인

파일을 바이러스 검사 중입니다.

이 파일은 다운로드할 수 없습니다