Automation
Terminate
Stops the run with your own message as soon as any row meets a condition — the rows go no further and later steps do not run.
When to use it
Use it as a guard before a load: stop when a quality check counted critical errors, when a file is empty of real data, or when a total does not reconcile.
In a pipeline
File InputRow CountTerminateSQL Server Output
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| Stop when | text | Yes | {critical_errors} > 0 |
| Message | text | — | The run was stopped by a Terminate step. |
Example
Stop before loading bad data
- Stop when={critical_errors} > 0
- Message={critical_errors} critical errors — not loading today
| file | critical_errors |
|---|---|
| orders.csv | 3 |
The run fails with "3 critical errors — not loading today", and the output step is skipped. With 0 critical errors the row passes on unchanged.
Worth knowing
- Stop when is a formula, as in Calculated Column: {Column} for values, $Variable for variables, && and ||, and functions such as AND(…), OR(…) and IF(…).
- The message can name columns too — they are read from the first row that met the condition.
- A Logging node downstream still runs and reports the stop, so its failure pin can send an alert.
- With no rows arriving nothing is checked and the run carries on; count the rows first (Row Count) to stop on an empty input.