Specific Error workflow does not work

[BramKn]

We got an error workflow set up to send emails. Sadly this isn’t working.
I’ve tested by creating a workflow that simply triggers the error node. While this error workflow was set up. This doesn’t work for this specific error workflow. When creating a new error workflow it does work.
Also removing the trigger node on this broken error workflow and recreating one, did not solve the issue.

error workflow settings:

workflow settings:

These are live workflows (of course the error workflow is not active)

Test workflow:

error workflow that doesn’t work:

error workflow that does work:

So replacing all the error workflows with a new one should work. But we do not want to change all the workflows we got if we can fix it any other way.

Information on your n8n setup

• n8n version: 209.4
• Database you’re using (default: SQLite): postgres
• Running n8n with the execution process [own(default), main]: main (queue)
• Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker

[Jon]

Hey @BramKn,

I have tested the workflow on my instance and it appears to be working as expected, It sounds like maybe something has gone wrong with the install at some point.

When you say it doesn’t work does it not trigger at all? It could be worth checking the logs to see if there is anything there that could be useful.

[BramKn]

Hey @Jon

Yeah it doesn’t get triggered (or atleast not visible in the executions for example)
when swapping the same test workflow to the other error workflow, it does work as expected.
So Yeah will check the logs on the server when I get the chance.

Thanks.

[BramKn]

Hey @Jon

So I had some time to check the issue.
The log shows that it was blocked due to permissions.

An attempt to execute workflow ID 33 as error workflow was blocked due to wrong permission

[Jon]

Hey @BramKn,

That is interesting, Did the workflow get made by a different user or did they upgrade then downgrade and upgrade again?

[BramKn]

Was created by another user indeed.

[Kam]

Sharing my own experience with Error Workflows:

We have several worflows activated for at least a year, and we have 1 Workflow monitoring all errors
We did upgrade to version 0.212.1 a couple of days ago, and since then, the Error workflow is not activated anymore.

I did find out that when we created this Error workflow, it had a PLAY node somewhere but not connected to the workflow, and everything was running fine.

Since upgrading n8n to version 0.212.1, this PLAY node is causing it to not run.
I did delete it, and all is fine now.

[MutedJam]

Hi @BramKn I am so sorry for the trouble. This appears to be a problem introduced with user management - it seems error workflows can’t be executed by all users.

Following another report, @krynble has worked on a fix (refactor: Change permission check to be based on workflow settings by krynble · Pull Request #5390 · n8n-io/n8n · GitHub) essentially allowing an error workflow to be executed depending on the “This workflow can be called by:” setting of the workflow.

This is currently awaiting a review and should hopefully be available soon.