Custom Action authentication debug

To check whether the request payload is correct, cross-check with the third party documentation whose endpoint you’re using. Also, try curl to check what error you’re receiving. It would be easier to debug.

​@Dex 666 

• Authentication and payload are tested separately — "Test successful" only confirms credentials/auth endpoint work, not that the actual request body sent per-profile is valid.
• A 400 means the server understood the request but rejected something in it — usually a parameter/body issue, not an auth issue.

Next steps to debug:

• Enable the error response payload in the custom action config so the actual CRM error message (not just the status code) becomes available under Contextual attributes > Journey Orchestration > Actions > [action] > errorResponse.
• Check for null/malformed dynamic field values on live profiles — Test Authentication runs on sample data, not real profile data, so a variable field resolving to null/empty/wrong type for certain profiles is a common cause that won't show up in testing.
• Additionaly test using the Postman/curl call to the public endpoint (RequestBin).

Relevant links:

• Use API call responses in custom actions / jo_status_code reference - https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configure-journeys/action-journeys/action-response
• AJO Error codes reference - https://experienceleague.adobe.com/en/docs/journey-optimizer/using/monitor/monitor-alerts-errors/error-codes-reference