Even better 'merge error' node including an 'No_Error' indicator

[LuI]

Merge Errors picks the 1st error it finds in the list of incoming errors and returns it as Error_Out. Fine for error handling.

Sometimes it is usefull to perform other steps independently if an error occured and handle all errors later, but a given sequence must be maintained. I found it usefull to have a wrapper around Merge_Errors that also returns a No_Error as constant:

This way one can wire the No_Error to other nodes doing their jobs and merging their errors together with other into the error hadler.

[LuI]

Forgot to insert an example on how to serialize prozesses using that improved_error_merge:

Step 1 is performed independently if an error came in. Step 2 dito, but not before step 1 finished. No error - neither the incoming nor any error of step 1 or 2 is skipped intentionally. Of course errors can also be aggregated and processed all together.

[AristosQueue (NI)]

Is this functionally equivalent to "Merge Error, then fork the wire, with the top fork passing though Clear Errors on its way to the next function"?  I can see the utility of having that in one node... I just want to make sure I understand the behavior you're asking for here.

[LuI]

Yep! Its just a little timesafer I have since 7.1., which does no longer directly work with the expandable merge error node

[Darren]

Any idea that has received less than 3 kudos within 3 years after posting will be automatically declined.