Can we please confirm that the condition "If there is no error" on the Decision tool recognizes and catches all HTTP error codes
Wynand Vermaak 3 weeks ago in Studio / Toolbox • updated 3 weeks ago • 1
We recently ran into a number of issues, and upon investigating we've come to the conclusion that the "If there is no error" condition on the Decision Tool doesn't catch all API HTTP errors - the ones we've experienced a number of times is 400, 404, 500, 503, 504.
I have attached a sample workflow, as an example, indicating the standard way we map our API GET or Post tools. Can you please use a similar setup during testing to confirm if all HTTP errors are recognized and caught?
Customer support service by UserEcho