HTTP 429 response code is rate limit/throttling. You are making too many requests in a given timeframe. You either need to implement some sort of sleep after making X amount of calls before making additional calls again or find a more efficient way to get the data via the APIs if possible. My guess is you have two aggregation endpoints, one to get the list of employees, and another sub-aggregation operation to get additional details about each employee fetched from the parent aggregation operation which will equate to a lot of calls in a small timeframe.
This is the actual cause and I’m still trying to fix this issue. Added retry after in an aggregation header, tried pagination too but the issue is same. Any suggestion how to resolve this issue.?
The Retry won’t help with the rate limit. You will need to review the parameters of the rate limit and attempt to fit your query within those parameters. The parameters will be something like X number of records per T timeframe. I believe the documentation that was linked above showed 1000 requests per 1 hour, so you’ll need to figure out how to fit within those parameters, or investigate with the software vendor on whether they can increase the limit for you (although this is not a common occurrence. )
Based on the rate limit referring to the cornerstone, I have changed the pagination. However, there is still error":“CSOD Too many requests.”,“code”:“429”,"
Wondering what will be the best way to limit the rate to resolve this issue?
after implementing sleep in after rule, additional users were able to pull however currently different 5** related error is coming. Could you please let me know if you have any insights for this? This is the error :
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner."