There are two Nodes that facilitate error handling directly - the Error Handler Node and the Throw Error Node.
The Error Handler Node can be configured to handle errors that happen anywhere in a Workflow, or configured to only handle errors for a certain group.
In addition, Error Handler Nodes can be configured to handle only a certain exception type. Exception types can be the internal exception types to .Net Core, or exception types you specify with the Throw Error Node.
The Error Handler Node is special because it doesn't participate in normal input/output execution flow. When an error occurs in the Workflow, the Workflow's execution path moves to an applicable Error Handler Node.
If an error occurs in your Workflow and there is no Error Handler Node to catch it, it will bubble up to the Runtime. The Runtime will log the error, and do the following, depending on the type of Workflow.
Uncaught Error Handling Behavior
The Function Caller Node that is calling the function will throw an error.
Execution of Job stops and is attempted again next time its scheduled.
Any Node can throw an error, but you can use the Throw Error Node to explicitly throw an error. Like the Handle Error Node, the Throw Error Node is special because it doesn't participate in normal input/output execution flow.
A Throw Error Node can be configured to throw an error of a specified type, which in this case coincides with the type handled in our above error handling example.