Workflow Agent erroring in External API call in one application but working in another
We have a custom workflow agent which uses multiple External Rest API calls. This Agent is developed and tested in the dev application, However, when this agent is imported to another application, it ends up in error exactly at External API call.
Following is the error message
Node GEOCODESHIPFROM failed with error: Request failed with status 403 and error resoponse family CLIENT_ERROR
The Input to the node seems to be same in both the application. (Refer to Screenshots)
Is there any role/privileges that dictates this behaviour?
Tagged:
0