Hi Colin, has this idea gotten any traction?
This issue of an HTTP action failing the whole workflow severely limits the action’s capability. Ideally if the workflow HTTP action receives a JSON based error message back one would expect the response to be parse-able to allow for graceful handling.
Are there any suggested workarounds?