Access response text of failed http actions in integration logs for ZIS
Feature Request Summary:
When an http action is unsuccessful (e.g. returns 400), I would like to see the response text in the integration logs and not just the code.
Description/Use Cases:
A ZIS app has multiple http actions. They can sometimes fail due to bad input and the error is caught as follows:
"SampleState": {
"Type": "Action",
"ActionName": "zis:sample_integration:action:zendesk.SampleApiCall",
"Parameters": {
"token.$": "$.connections.zendesk.access_token",
},
"Catch": [{
"ErrorEquals": ["States.ALL"],
"ResultPath": "$.failure_response",
"Next": "Terminator"
}],
"ResultPath": "$.success_response",
"Next": "NextState"
}
"Terminator": {
"Type": "Fail",
"Error": "Unexpected Response",
"Cause": "$.failure_response"
}
Unfortunately, the cause shown in the log is as follows:
map[Cause:external action failed due to status code: 400 Error:customError]
For troubleshooting, developer has to copy the input from the logs, replicate the indicated action in terminal/postman while carefully filling all the payload placeholders with input data. God forbid if some of it depends on responses to previous states. Eventually a helpful error description explains everything in the response text:
{
"errors": [
{
"id": "0x123",
"code": "ExternalIDExists",
"title": "A different external ID is present on the user"
}
]
}
It would be great to have access to this response text and store it in the ResultPath
instead of it being overridden by $.Error
and $.Cause
objects.
Business impact of limitation or missing feature:
This is crucial to improve and speedup development of ZIS integrations.
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
0 Kommentare