# Parallell execution semantics

**URL:** <https://community.n8n.io/t/parallell-execution-semantics/82089>\
**Category:** Feature Requests\
**Created:** [February 26, 2025, 11:27am UTC](https://community.n8n.io/t/parallell-execution-semantics/82089 "2025-02-26T11:27:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Wicked\_AI\_Ware](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/wicked_ai_ware/32/59088_2.png) [@Wicked\_AI\_Ware](https://community.n8n.io/u/Wicked_AI_Ware)\
**Post date:** [February 26, 2025, 11:27am UTC](https://community.n8n.io/t/parallell-execution-semantics/82089/1 "2025-02-26T11:27:05Z")

</div>

## The idea is:

These days all languages support parallel execution.  
E.g. Java had this since Java5 I remember.  
(Of course behind the scenes, CPU power is distributed between different cores and different threads - which makes it in reality more / less “really” parallel - but this matters not for the user).

I do believe it can matter for the user to have, in n8n, a construct to simulate such parallellisme.  
I believe this could be done with just 2 Nodes and 2 variables:

- A splitting Node (from where parallel paths start), simultaneously
- A Merging Node (where parallel paths come together)
- A boolean variable added to Nodes in a parallel path to signal whether or not to execute this Node in atomic way (although I would advocate to default this to “Yes”; to avoid a Node execution is broken up).
- A (boolean) Variable at the Merge Node signaling whether to wait for all paths to come together before proceeding or not (i.e. is a simultaneous exit required? Sometimes all results need to come in before proceeding, not just partial results).  
What I’m not clear about yet is what to do @error (e.g. 1 Node keeps its Thread in wait state, blocking the entire setup → Ignore or throw error/…? Maybe this (and a timeout) could also be set in the Merge/Split Node.

## Use case:

Cf. the many questions on this here.

---

<div class="post-metadata">

**Author:** ![solomon](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/solomon/32/43567_2.png) [@solomon](https://community.n8n.io/u/solomon)\
**Post date:** [February 26, 2025, 1:03pm UTC](https://community.n8n.io/t/parallell-execution-semantics/82089/2 "2025-02-26T13:03:43Z")

</div>

That’s very interesting.

Right now n8n has an execution order for multi-branch workflows, based on the position each branch has in the canvas.

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/8/5/850dc9cb3dd385ab6da35abe84cab9ce12630ce7.png)

But you can also have parallel executions if you use **[sub-workflows](https://docs.n8n.io/flow-logic/subworkflows/)**.

When setting up your “Execute workflow” node, you disable the option “Wait for Sub-workflow completion”

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/0/c/0c1b8fa1379ccc78797bb9e4f783304b4412dbf7.png)

Meaning that the sub-workflow will execute in parallel.

---

<div class="post-metadata">

**Author:** ![Wicked\_AI\_Ware](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/wicked_ai_ware/32/59088_2.png) [@Wicked\_AI\_Ware](https://community.n8n.io/u/Wicked_AI_Ware)\
**Post date:** [February 26, 2025, 1:55pm UTC](https://community.n8n.io/t/parallell-execution-semantics/82089/3 "2025-02-26T13:55:45Z")

</div>

Yeah - I know this is what we currently have. But this is serial execution. Following a graphic criterion. The proposed approach would

- be parallel execution
- not be based on graphical position (even if also for parallel execution, such visual order can be kept to repeatedly cycle through the Threads)
- leverage the underlying language concurrency semantics for its execution

As… no matter how cool n8n is, this omission dates n8n a bit in our era of multi-core, multi-thread, and a universe in which even men multitask haha.

---

<div class="post-metadata">

**Author:** ![Renza\_Polza](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/renza_polza/32/136118_2.png) [@Renza\_Polza](https://community.n8n.io/u/Renza_Polza)\
**Post date:** [November 9, 2025, 2:06pm UTC](https://community.n8n.io/t/parallell-execution-semantics/82089/4 "2025-11-09T14:06:35Z")

</div>

This only works if you aren’t dependent on the executions that need to happen in parallel.

Example:  
You listen to sensor data, and when it comes in, you need to perform multiple computationally intensive analyses and then combine them into a report.

In my case, I perform video processing on different outputs, and then after the processes have finished, I must perform checks on all of them. Only if they succeed should the process continue and start moving the files to a different server. If one of the checks fails, everything must be halted, and manual intervention is required.

Executing in parallel will reduce the processing time from ~7.5 hours to ~6 hours. That is a massive gain.

I understand that there are workarounds for this, but I moved to n8n from my old scripts/services to make the automations easier to understand, and all those solutions just make it a mess.
