Error workflow at 2.x version

Questions
1

Hi, as in v1.x, the error workflow shouldn’t be enabled and will only be triggered by other workflow when error occur.

But after I upgrade the N8N to v2.0.2, the error workflow also being “published”. I assume this published status is the same meaning as “Active” in v1.x.

What is the logic in 2.x dealing with error workflow? Should I publish it and unpublish it?

Thanks

2

AFAIK in n8n 1.x you didn’t need to activate an error workflow. As soon as you added an error trigger node, it was active automagically.
From n8n 2.0 an error workflow needs to be published in order to work (even if Error Trigger node documentation | n8n Docs tells something different - my error workflow didn’t trigger when it was not published).

But if you upgrade your n8n instance from n8n 1.x to 2.x, your existing error workflows are already published (at least in my case I saw they were already published).

3

got it, so I need to keep the error workflow at published state.

Thanks

1 Like