Try / Catch

Try / Catch keeps a failure inside a handled branch instead of failing the whole run.

Purpose and use: Route an already error-shaped input to a catch branch. It is not a language-level try/catch around upstream execution.

Configuration: No node-specific fields (required: none; optional: none).

Input/output and routing: One input; outputs main and catch. Routes to catch only when input has truthy error or errorMessage; otherwise main. Connect downstream edges to the named handles.

Expressions: No node-specific expression settings. Upstream configuration can use expressions, but this router checks the resulting input object.

Errors/effects: An upstream node with onError=stop aborts before Try / Catch. To route a failure here, the upstream node must continue and provide an error-shaped value. The router itself has no write effect; catch-path nodes may.

Example configuration — fields validated against the 1.1.1 node schema; replace the identifiers with your own: {"type":"logic_try_catch","data":{"label":"Try / Catch","config":{}}}. Expected result: the catch route is taken only when the input carries an error marker.