QOL: Stop Workflow EARLY But Do NOT Throw Error

Feature Requests
1

Guys, I’m struggling here… there are times during my workflow where I need the workflow to HALT early. In those cases, I don’t want it to evaluate any other paths.

The only built-in mechanism I see is Stop and Error node – but it’s not an error! I really don’t want early stoppage of workflows to be treated as an error. I can’t even silently “catch” this error to suppress further error reporting. Is there any other way I can deal with this?

I really wish there was a Stop and DONT Throw Error node type, to be honest.

Any ideas?

2

Okay, after thinking about this problem a LOT more, I think the only equivalent to Stop and DONT Throw Error would be:

  • Add a Filter node to each and every “path” in your workflow
  • The logic in the Filter node should check “termination” conditions based on earlier node executions
  • If those checks fail, then the Filter node will silently halt further execution

So the gist is:

  • n8n does have this capability
  • but it’s poorly named
  • a generic Stop and DONT Throw Error would be to simply create a Filter node where the condition check is like {{ true }} == {{ false }} – which would always evaluate to false