# Handling processes out of HTTP IN calls in parallel

**URL:** <https://discourse.nodered.org/t/handling-processes-out-of-http-in-calls-in-parallel/83689>\
**Category:** General\
**Created:** [13 December 2023 17:46 UTC](https://discourse.nodered.org/t/handling-processes-out-of-http-in-calls-in-parallel/83689 "2023-12-13T17:46:47Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [13 December 2023 17:53 UTC](https://discourse.nodered.org/t/handling-processes-out-of-http-in-calls-in-parallel/83689/2 "2023-12-13T17:53:58Z")

</div>

2 possible Solutions

- A Native RED Flow by @Colin ( think I have the right version)  
[Wait for payload to finish flow before passing another payload](https://discourse.nodered.org/t/wait-for-payload-to-finish-flow-before-passing-another-payload/64171)

- A set of Nodes I Built to facilitate this need with some extras  
[node-red-semaphore-plus (node) - Node-RED](https://flows.nodered.org/node/@marcus-j-davies/node-red-semaphore-plus)

---

_[View the full topic](https://discourse.nodered.org/t/handling-processes-out-of-http-in-calls-in-parallel/83689)._