Control node execution order

I have created the following workflow section. How can i make sure the first line of nodes finished even if the second one fails? In this case it basically separates if a create or update operation needs to be executed.

Information on your n8n setup

  • n8n version:0.225.1
  • Database (default: SQLite):postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):cloudron

In the node settings for your http request you can ignore errors. Otherwise if you need to see failed workflows, a hacky way is to just put a couple of No Operation nodes before your troublesome http request to ensure it runs last

1 Like

Thank you very much :slight_smile: Is there no better way than turning off error handling or a relatively ugly workaround? I though maybe there is a magical combination of using merges. But that was my hope speaking :smiley:

You can also use the Merge node to run your second branch after the first one like so:

This uses the Choose Branch → Wait for Both Inputs to Arrive setting of the Merge node:



@MutedJam Thank you very much. The idea i great but since there is an if to separate routes one will very likely never be entered leading to the following state:

The final node is never reached due to the waiting for input 1

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.