When using the HTTP action to call a REST API, if there is an HTTP error response (e.g. 4xx or 5xx status code) then often the response body contains an explanation of what the problem was. However, Workato discards that response and only saves the status code.
It's really frustrating debugging a failed recipe when I can't see the error response, and when I'm calling a 3rd party system where I don't have access to the logs of that system.
If an HTTP request returns an HTTP error response, I'd like to see the response body when looking at the job.
I understand that in some cases the response might be a large HTML error page with no useful information. If this is likely to be a problem, then only storing JSON or plain text responses would be fine for me. (Although it should probably store the response's Content-Type in any case, so we can see why it didn't store the response if it was filtered out by content-type.)
1 person likes this idea
B
Bernardo Dizon
said
over 6 years ago
Duplicate
1 person likes this
Still can't find your solution?
Send us a ticket,
we will try our best to assist you with your problem
Menzies Prod
See HTTP error responses
When using the HTTP action to call a REST API, if there is an HTTP error response (e.g. 4xx or 5xx status code) then often the response body contains an explanation of what the problem was. However, Workato discards that response and only saves the status code.
It's really frustrating debugging a failed recipe when I can't see the error response, and when I'm calling a 3rd party system where I don't have access to the logs of that system.
If an HTTP request returns an HTTP error response, I'd like to see the response body when looking at the job.
I understand that in some cases the response might be a large HTML error page with no useful information. If this is likely to be a problem, then only storing JSON or plain text responses would be fine for me. (Although it should probably store the response's Content-Type in any case, so we can see why it didn't store the response if it was filtered out by content-type.)
1 person likes this idea