VamimiOpen VamimiAI

Automation documentation

n8n Error Workflow Not Triggering? 6 Causes and Fixes

Why an n8n error workflow does not run when a workflow fails, how to check each cause in a few minutes, and how to test it safely before a client relies on it.

By VamimiAI team · · 3 min read

When an n8n error workflow does not trigger, the cause is almost always one of six things: the failing workflow does not point to it, it does not start with an Error Trigger, the failure happened in a run you started by hand, the node was set to continue instead of fail, the failure was inside a sub-workflow, or the error workflow ran and failed itself. Check them in this order; the first three cover most cases.

1. The failing workflow does not point to it

The link is set on the workflow that fails, not on the error workflow. Open the failing workflow, open Workflow settings, and check that Error Workflow names your error workflow. A new workflow, a duplicated one and one imported from a file start with no error workflow set, so a workflow you copied from a working one may not have it.

2. The error workflow does not start with an Error Trigger

An error workflow is an ordinary workflow whose first node is the Error Trigger. If it starts with a webhook or a schedule instead, n8n has nothing to call when a run fails.

3. You tested by running the workflow by hand

n8n starts the error workflow for runs started by a trigger: a schedule, a webhook, an app event. A failure in a run you start yourself from the editor shows the error on the canvas instead. This is the most common reason people think it is broken.

To test it properly, put a Stop and Error node where you want the failure, make sure the workflow runs from its trigger (call the production webhook URL, or let the schedule fire), and watch the error workflow's executions.

4. The node was set to continue, not to fail

A node whose On Error setting is Continue or Continue (using error output) does not fail the run. The run carries on, finishes, and the error workflow never hears about it. That is intended: the failure is handled by the path you built. If you also want an alert, send one from the error output, or end that path with a Stop and Error node so the run fails on purpose.

5. The failure happened inside a sub-workflow

When a workflow calls another one with Execute Workflow, the failure happens in the sub-workflow. Set the error workflow on the sub-workflow as well, and check the executions of both, so a failure is caught wherever it happens.

6. The error workflow ran, and failed too

Open the error workflow's own executions. If its Slack, email or ticket step uses a login that has expired, the alert fails silently. Keep the error workflow small: one alert step with a retry, using a login that is not shared with the workflows it watches.

Make it part of the handover

Before you hand a workflow to a client, every production workflow should name the error workflow, and the error workflow should have been tested from a real trigger. Importing the workflow into VamimiAI's n8n workflow diagram flags a workflow with no error workflow set and draws each call to an outside service that nothing protects as a red end, so you can see what is still unprotected. The n8n error handling guide covers retries and error outputs, and the handover document tells the client where failed runs show up.

Questions

Does the n8n error workflow run on manual executions?

No. It runs when a run started by a trigger fails. To test it, run the workflow from its trigger with a Stop and Error node where you want the failure.

Do I need one error workflow per workflow?

No. One error workflow can serve every workflow of a client; each workflow names it in its own settings.

Why does my workflow finish successfully even though a node failed?

The node's On Error setting is Continue or Continue (using error output), so the failure is handled by the path you built and the run does not fail. Send an alert from that path, or end it with a Stop and Error node.

Tools for this