# One to Many Request Delay

**URL:** <https://connective.celigo.com/t/one-to-many-request-delay/413>\
**Category:** Integrator.io\
**Tags:** database, performance, error-handling, flow-builder\
**Created:** [July 19, 2023, 1:40pm UTC](https://connective.celigo.com/t/one-to-many-request-delay/413 "2023-07-19T13:40:20Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![yashkumar](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/yashkumar/32/9271_2.png) [@yashkumar](https://connective.celigo.com/u/yashkumar)\
**Post date:** [July 19, 2023, 1:40pm UTC](https://connective.celigo.com/t/one-to-many-request-delay/413/1 "2023-07-19T13:40:20Z")

</div>

Hello All,

I need your valuable insights! While performing one-to-many requests on a database record, we're experiencing overload issues. Out of four requests, one often fails, but retrying the failed request succeeds in updating the record.

To address this, I've created a Celigo flow for automatic error retries. However, I'd love to hear if any of you faced similar challenges and how you tackled them.

Also, can we add delay while making one to many request?

Please share your experiences and ideas.

---

<div class="post-metadata">

**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\
**Post date:** [July 19, 2023, 1:59pm UTC](https://connective.celigo.com/t/one-to-many-request-delay/413/2 "2023-07-19T13:59:27Z")

</div>

@yashkumar what database type are you using and what is the concurrency level on your connection settings?

---

<div class="post-metadata">

**Author:** ![yashkumar](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/yashkumar/32/9271_2.png) [@yashkumar](https://connective.celigo.com/u/yashkumar)\
**Post date:** [July 19, 2023, 2:27pm UTC](https://connective.celigo.com/t/one-to-many-request-delay/413/3 "2023-07-19T14:27:32Z")

</div>

We are making post request to Microsoft Dynamics365 business central. Concurrency is default

---

<div class="post-metadata">

**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\
**Post date:** [July 19, 2023, 3:10pm UTC](https://connective.celigo.com/t/one-to-many-request-delay/413/4 "2023-07-19T15:10:19Z")

</div>

@yashkumar by default do you mean the field is blank? If so, you should specify a concurrency level so that we don't make too many requests at a time.

---

<div class="post-metadata">

**Author:** ![yashkumar](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/yashkumar/32/9271_2.png) [@yashkumar](https://connective.celigo.com/u/yashkumar)\
**Post date:** [July 19, 2023, 3:18pm UTC](https://connective.celigo.com/t/one-to-many-request-delay/413/5 "2023-07-19T15:18:37Z")

</div>

Are you referring to the below field on the import to define the concurrency here ? Also Unlike NetSuite we don't have an option to define concurrency for the business central connection.

 ![5301043caa20740200000001-2e5d33cf881044ba912150a6c359e4ae.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/b/b8325151c6e712eed250a5581ff8ffd0fc240d6c.png)

---

<div class="post-metadata">

**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\
**Post date:** [July 19, 2023, 3:21pm UTC](https://connective.celigo.com/t/one-to-many-request-delay/413/6 "2023-07-19T15:21:40Z")

</div>

@yashkumar concurrency level is on the connection resource itself and not on import/export/flow resources. Here is a screenshot of a BC 365 concurrency setting on the connection level.

 ![5301043caa20740200000001-25b178e789984cd2b0c30516c6c55b55.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/9/9dfe451a37a82a2c06908bcc7cd72f33e3bc3c5a.png)

Also, here are a few good docs explaining how concurrency works:

- [https://docs.celigo.com/hc/en-us/articles/360043926372-Configure-connections-to-optimize-throughput-and-governance](https://docs.celigo.com/hc/en-us/articles/360043926372-Configure-connections-to-optimize-throughput-and-governance)
- [https://docs.celigo.com/hc/en-us/articles/360043927292-Fine-tune-integrator-io-for-optimal-performance-and-data-throughput](https://docs.celigo.com/hc/en-us/articles/360043927292-Fine-tune-integrator-io-for-optimal-performance-and-data-throughput)

---

<div class="post-metadata">

**Author:** ![yashkumar](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/yashkumar/32/9271_2.png) [@yashkumar](https://connective.celigo.com/u/yashkumar)\
**Post date:** [July 19, 2023, 3:33pm UTC](https://connective.celigo.com/t/one-to-many-request-delay/413/7 "2023-07-19T15:33:30Z")

</div>

Thanks Tyler! I though there is something different setting in case of one-many request.

I'll try with this