# HTTP Node: limiting concurrency

**URL:** <https://community.n8n.io/t/http-node-limiting-concurrency/2451>\
**Category:** Feature Requests\
**Created:** [September 25, 2020, 3:02pm UTC](https://community.n8n.io/t/http-node-limiting-concurrency/2451 "2020-09-25T15:02:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Miquel\_Colomer](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/miquel_colomer/32/18606_2.png) [@Miquel\_Colomer](https://community.n8n.io/u/Miquel_Colomer)\
**Post date:** [September 25, 2020, 3:02pm UTC](https://community.n8n.io/t/http-node-limiting-concurrency/2451/1 "2020-09-25T15:02:11Z")

</div>

Hi,

We are testing HTTP Node and node is launching all requests concurrently. This can exceed IP rate limit easily for any API.

An option to define concurrency limit could be useful to avoid this kind of problems.

Could you add this option to HTTP node?

Thanks!

---

<div class="post-metadata">

**Author:** ![Miquel\_Colomer](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/miquel_colomer/32/18606_2.png) [@Miquel\_Colomer](https://community.n8n.io/u/Miquel_Colomer)\
**Post date:** [September 26, 2020, 11:08am UTC](https://community.n8n.io/t/http-node-limiting-concurrency/2451/2 "2020-09-26T11:08:56Z")

</div>

I reply myself.

You can put a SplitInBatches node before any request and defining the required batch number, depending on the service concurrency limit per user account. Working task looks this way:

 ![image](https://europe1.discourse-cdn.com/n8n/original/2X/5/53f2006f344eac55d6716a1ebae879266ebacb6c.png)

---

<div class="post-metadata">

**Author:** ![mcnaveen](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mcnaveen/32/53924_2.png) [@mcnaveen](https://community.n8n.io/u/mcnaveen)\
**Post date:** [September 26, 2020, 11:38am UTC](https://community.n8n.io/t/http-node-limiting-concurrency/2451/3 "2020-09-26T11:38:55Z")

</div>

Instead of keep pinging the endpoint continuously in the loop, I suggest you add a wait time before each request.

You can use the Function Node to achieve. This will add 2 Second wait time before each request.

The Function Node should be right before the HTTP Request Node. In case you want to add extra time simply edit **const waitTimeSeconds = NUMBER;** with your desired choice of number.

```
const waitTimeSeconds = 2;

return new Promise((resolve) => {
  setTimeout(() => {
    resolve(items);
  }, waitTimeSeconds * 1000);
});

```

> Here 2msx1000 = 2 Seconds Wait time

---

<div class="post-metadata">

**Author:** ![Miquel\_Colomer](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/miquel_colomer/32/18606_2.png) [@Miquel\_Colomer](https://community.n8n.io/u/Miquel_Colomer)\
**Post date:** [September 26, 2020, 11:40am UTC](https://community.n8n.io/t/http-node-limiting-concurrency/2451/4 "2020-09-26T11:40:03Z")

</div>

Thanks @mcnaveen.  
Nice idea!

---

<div class="post-metadata">

**Author:** ![mcnaveen](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mcnaveen/32/53924_2.png) [@mcnaveen](https://community.n8n.io/u/mcnaveen)\
**Post date:** [September 26, 2020, 11:40am UTC](https://community.n8n.io/t/http-node-limiting-concurrency/2451/5 "2020-09-26T11:40:32Z")

</div>

You’re welcome 💪 Let’s grow together.