# Wait node causing multiple executions?

**URL:** <https://community.n8n.io/t/wait-node-causing-multiple-executions/234316>\
**Category:** Questions\
**Created:** [December 11, 2025, 2:45am UTC](https://community.n8n.io/t/wait-node-causing-multiple-executions/234316 "2025-12-11T02:45:57Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![mohamed3nan](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mohamed3nan/32/188347_2.png) [@mohamed3nan](https://community.n8n.io/u/mohamed3nan)\
**Post date:** [December 11, 2025, 9:33pm UTC](https://community.n8n.io/t/wait-node-causing-multiple-executions/234316/7 "2025-12-11T21:33:15Z")

</div>

Maybe this is related to the bug mentioned here?

> [@Announcing n8n version 2.0 - coming soon!](http://community.n8n.io/t/announcing-n8n-version-2-0-coming-soon/226475/124):
>
> The issue with the subworkflow’s waiting node is fixed. Yet, when there are multiple waiting nodes, the parent only waits for the first and uses the result of the node preceding the second waiting node. Is this intended behavior or a bug? I want to see the parent wait for all waiting nodes and take the final result of the subworkflow.

> [@Announcing n8n version 2.0 - coming soon!](http://community.n8n.io/t/announcing-n8n-version-2-0-coming-soon/226475/125):
>
> Thanks a lot for reporting this. It sounds like a bug, and we are looking into it directly.

---

_[View the full topic](https://community.n8n.io/t/wait-node-causing-multiple-executions/234316)._