Error Trigger Functionality in N8N local

Questions
1

Why does “Error Trigger” does not work in the local N8N workflow. I created the error workflow basic with Error Trigger and a Google sheet to enter error details. I included this to another flow where I added error generating text. Both these were published but the error trigger workflow is not getting triggered. All these done in local N8N with Docker container. Any help or suggestion.

2

Did you do this?

image
image1239×578 19.2 KB

1 Like
4

Hi @Anshul_Namdev

OP already stated

5

since you’re on Docker — error triggers can be finicky there. a few things worth checking: does the error workflow actually run if you trigger it manually first? also verify the error trigger node itself is set to “catch all errors” and not filtered to a specific error code. sometimes the link between the main workflow and the error workflow only registers properly after a fresh activation — try deactivating both workflows, then re-activating the error workflow first, then the main one.

1 Like
6

Yes already did that part

7

Thanks for all your advice, I did all that

  1. error workflow actually run if you trigger it manually first. Yes
  2. error trigger node is the basic, no filtering linked
  3. deactivating both workflows, multiple times

I think there is some minor aspect I am missing. Attaching both the workflows. Hope this helps to guide me further.

Note: The “Edit Field” node within the “Google Oath Connect” workflow has the error in JSON, which should initiate the ErrorWorkflow.

Google OAuth Connect.json (8.5 KB)

ErrorWorkflow.json (3.7 KB)

1 Like
8

I got this resolved.

I was using the Test URL and not the PROD URL of the Webhook. Now its working file and properly recording the error data. Thanks to all your help and support. Great team support.

1 Like
9

glad you got it sorted! test vs prod webhook URL catches everyone at some point — good find.

1 Like