Error handling

​

The three error modes

Every processor tool has an On error setting that controls what happens when a record fails to process.

​

Choosing the right mode

Use Stop when:

• A failure means something is fundamentally wrong with the tool configuration
• You want to catch issues early before they affect many records
• The tool is making irreversible changes (like deleting records) and you want to be cautious

Use Continue or Skip when:

• Some records are expected to fail (missing values, unusual formats)
• You want to process as many records as possible and review failures separately
• The failures are isolated and don’t indicate a systemic problem

​

Viewing errors

Failed records are logged in the execution log with a timestamp, the record ID, and the error message. Review the log after a run to understand what went wrong. The run metrics show the split between succeeded and failed records at a glance.

​

Common error causes

​

Re-running after errors

After fixing the underlying issue, you can re-run the tool. If you have a “Skip already processed” or “Skip non-empty output” option, enable it to skip records that succeeded on the first run and only reprocess the ones that failed. Alternatively, filter the tool to run only on the specific records that failed by adding a filter condition on the record IDs or a status field you set during the failed run.

​

Common questions