Question about using wait nodes

Questions
,
1

So, I’ve been toying a bit with the wait node, and searching a bit on how to make workflows more “asynchronous”, and came across the following post : Wait Node Delays Node in Different Connection from Executing

While I know that that is expected behaviour and why, would it be possible to have a workaround to the result the poster wanted, so as to, for example, have one “path” executed and at one point having a wait node waiting for a callback, while another path would go on and be executed?

Information on your n8n setup

  • n8n version: 1.36.1
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own, main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Windows 11
2

hello @Carrico

n8n does not execute nodes asynchronously. They all executed in an order. That order depends on the n8n version though.

For your task, you should split the workflow into smaller ones and execute sub-workflows one after another with the option “Wait for sub-Workflows completion” turned off.

2 Likes
3

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