We are using the SEQUENCE based error handling approach. When there is an error in the “logic” SEQUENCE, the “error” SEQUENCE is executing as expected.
However, the “exception” is still logged in the IS Error Log and the exceptionInfo information is presented to an Exception Event Handler (if one has been defined). From the Java perspective, this does not appear obvious since we appear to have “consumed” the exception (e.g. via the “error” SEQUENCE).
Is there a way to not have the exceptionInfo information logged in the IS Error Log or passed to the defined Exception Event Handler(s) when the Flow Service has already “handled” the error/exception?