# Exact Online 429 – Too Many Requests

**URL:** <https://community.cdata.com/t/exact-online-429-too-many-requests/285>\
**Category:** Data Sources\
**Tags:** exact-online, article\
**Created:** [July 25, 2023, 6:14pm UTC](https://community.cdata.com/t/exact-online-429-too-many-requests/285 "2023-07-25T18:14:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Luçjano\_Capo](https://sea3.discourse-cdn.com/cdata/user_avatar/community.cdata.com/lu%C3%A7jano_capo/32/1638_2.png) [@Luçjano\_Capo](https://community.cdata.com/u/Lu%C3%A7jano_Capo)\
**Post date:** [July 25, 2023, 6:14pm UTC](https://community.cdata.com/t/exact-online-429-too-many-requests/285/1 "2023-07-25T18:14:11Z")

</div>

Exact Online is notorious for its API limitations. If these limits are reached, the API throws HTTP 429 - Too Many Requests. More information about such limitations can be found in [Exact Knowledge Base](https://support.exactonline.com/community/s/knowledge-base#All-All-DNO-Simulation-gen-apilimits).&nbsp;  
A possible workaround is setting two connection properties (_MaximumRequestRetries_ and _RetryWaitTime_) through the _Other_ property in the driver configuration, to tweak how the retry logic works.

- _MaximumRequestRetries_ is the maximum number of times to retry a request if we get the error, while

- _RetryWaitTime_ is how long to wait before retrying a request in milliseconds.

Below is a screenshot that demonstrates how to set these properties and their corresponding values:

 ![391738c1-6be5-48b8-af2c-c14939a82580.png](https://us1.discourse-cdn.com/cdata/original/2X/9/968d69ee6990df1bb0e21a7b3c71a3f1637a116e.png)

The other recommendation would be to use a [custom OAuth App](https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdn.cdata.com%2Fhelp%2FDYJ%2Frssis%2Fpg_oauthcustomappcreate.htm&data=05%7C01%7Csupportsent%40cdata.com%7C25d8b4c03f644ed3078908db7ba22114%7Cbf6e4267a9fb419bae7b7586fab0ff66%7C1%7C0%7C638239708547820011%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=e8tmnsJItApP1C3hqofWgUlX%2FqJYyfaqtADFyJ6cEMA%3D&reserved=0) since our embedded app has a much smaller API limit.
