Workflow execution error but did not trigger Error Trigger

Questions
1

We have set up the Error Trigger so that when the main flow has an error, it will send a message by SendGrid.

We encountered an error at 08/15 00:06 and 08/14 19:06. When executing the main flow, there is an error, but no error information, and I can’t see which node is causing the error. The Error Trigger did not trigger as well.

Although the next following execution runs were successful, I would still like to know how we can avoid this issue. Thanks!

The workflow

image
image1795×854 115 KB

Information on your n8n setup

  • n8n version: 1.101.2
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
2

Hi MC and welcome to the community.

I have the Error workflow as a separate workflow and specify it in the source workflow settings:

image

I can see the documentation says that, if the Error Trigger is within the workflow, then it should be triggered “by default” (See here). So it should work. The docs also say that the Error trigger wont trigger if this is a manual execution - does not look like the case from your screenshot.

My suggestion would be to create a separate workflow withe the Error Trigger and your SendGrid node and then put the name of that workflow in your main workflow Settings as the “Error Workflow”. If that works then might be worth raising a bug request for the in-workflow Error Trigger fail.

Simon

3

Hi Simon,

Thanks for the info. I will give it a try :slight_smile: