Need Generic Catch Error Mechanism within Main Workflows about n8n HOT 5 CLOSED

Hey @dkindlund,

I like the idea but we use GitHub to track bugs not feature requests, would you be able to create this on the support forum which will allow the community to comment and vote on the request.

For now as there is no bug here I am going to mark this as closed.

from n8n.

Just fyi. Before n8n checks if an Error Workflow is set, it checks if the same workflow contains an Error Trigger node. If it does, it will use that one. Meaning if you add an Error Trigger node to a workflow it becomes its own Error Workflow. But important to remember that it will still be two different executions.

from n8n.

Just fyi. Before n8n checks if an Error Workflow is set, it checks if the same workflow contains an Error Trigger node. If it does, it will use that one. Meaning if you add an Error Trigger node to a workflow it becomes its own Error Workflow. But important to remember that it will still be two different executions.

^ Thanks for the clarification, @janober !

from n8n.

@janober , by the way, is there a way to easily pass data from the first execution over to the second execution (the Error Workflow)?

from n8n.

@Joffcom , thanks for the sanity check -- I've re-posted this item here then:
https://community.n8n.io/t/need-generic-catch-error-mechanism-within-main-workflows/42799

from n8n.