Why Does the Wait Node Block Other Executions in n8n Workflows?

I have a workflow in n8n that may trigger simultaneously for the same entity from different event types.

I added a Wait node for one event type to prevent interference, but it appears that the Wait node is blocking the execution for the other event type as well. As a result, both executions proceed to run the same steps concurrently.

I considered two workarounds:

1. Duplicating the workflow (one per event), which isn’t ideal since both workflows perform the same tasks.
2. Implementing a message broker.

My question is: why does the Wait node block the other execution? Notably, when I replace it with a Code node using an async sleep, the execution proceeds as expected while the other process handles its own task.

My current n8n setup is as follows:

• n8n version: 1.69.2
• Database (default: SQLite): Postgres
• n8n EXECUTIONS_PROCESS setting (default: own, main): main
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
• Operating system:

BASHCopied
cat /etc/os-release

Why is the behavior different when using the Wait node compared to an async sleep in a Code node?