Automation
Error Handler
Catches a failure of the step before it (or of any step before it) so the run carries on: the rows that step was working on leave by the Error pin, with Failed Step and Error columns; rows from steps that worked leave by OK.
When to use it
Use it when a failure should be set aside for review — written to an error file, sent as an alert — rather than stopping the whole run.
In a pipeline
File InputType ConversionError HandlerExport CSV
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| Catch errors from | select | — | node |
| On error | select | — | route |
Example
Set a failed batch aside
- On error=Send the rows to the Error pin
| Id | Amount |
|---|---|
| 1 | 12.50 |
| 2 | n/a |
| Id | Amount | Failed Step | Error |
|---|---|---|---|
| 1 | 12.50 | Type Conversion | "n/a" is not a number |
| 2 | n/a | Type Conversion | "n/a" is not a number |
Worth knowing
- The failed step still shows red on the canvas, but the run counts as a success: the handler took the failure in.
- Catch errors from: Any step before it covers every step upstream of the handler, not only the one wired to it.
- Connect a Logging node or an Export to the Error pin to keep a record of what failed.
- Drop the rows and carry on discards them; the node's note still says what failed.