n8n check · error handling
n8n Error Handling: Find Missing Failure Paths
A production workflow needs a deliberate place for failures to go. This check explains what an exported n8n graph can show about error behavior, failure paths, and partial completion.
What is this risk?
n8n provides node-level error behavior such as continuing with regular output or using an error output, and a workflow can be configured with an Error Workflow. These controls answer different failure-handling questions.
A static review asks whether the exported graph makes failure routing visible around meaningful side effects and conditional branches. It does not assume that an unshown path is safe or unsafe at runtime.
Typical failure pattern
A partial failure with no deliberate destination
- Incoming event
- External write or node failure
- Continue-on-error or an unhandled branch
- Green-looking completion, dropped item, or no visible recovery owner
Why it matters
- A workflow can continue after an item fails and leave the business process looking complete when a write or notification never happened.
- A write can succeed before a later node fails, leaving partial state that needs reconciliation rather than a blind replay.
Auturance signals
WL003Errors may be converted into successful execution paths
This is the current scanner signal associated with this check.
WL008External side effects have no visible failure handling
This is the current scanner signal associated with this check.
WL005Conditional path may end silently
This is the current scanner signal associated with this check.
What Auturance checks
- Flags continue-on-error behavior when the path can reach a detected external side effect.
- Flags external side effects without a configured workflow error handler or connected error-output handling.
- Flags conditional nodes whose main output paths are not visibly handled.
What Auturance cannot determine
- It cannot execute the workflow or inspect the contents and runtime behavior of an Error Workflow.
- It cannot prove that an alert, rollback, compensation, or downstream recovery action succeeds.
- A static graph may not include operational ownership, external-system state, or controls outside the export.
How to reduce the risk
- Choose explicitly whether a node should stop, continue with a deliberate partial-success rule, or route an error output.
- Configure and test a workflow-level Error Workflow or a connected alert, persistence, recovery, or Stop And Error path.
- Run failure tests after each important external write and document how partial state is reconciled.
Related checks
Related resource
Read the n8n workflow audit guide for the broader production-readiness review.
Related guide
See what your workflow reveals
Upload an authorized n8n export and review the static signals in its actual graph.