throttling problem

  • 1
  • Problem
  • Updated 5 months ago
hi,

i read and followed all your articles about throttling, but still i'm getting 429 from you, 
although i didn't reach the rate limit.
https://developer.ringcentral.com/api-docs/latest/index.html?_ga=2.28902133.890627266.1513606733-126...
http://ringcentral-faq.readthedocs.io/en/latest/api_usage_plan/#usage-plan-faq

i did a lot of digging, until i found the following post
https://devcommunity.ringcentral.com/ringcentraldev/topics/ringcentral-csharp-handling-429-exception...
which specifies, that in addition to the general rate limit, there's also a limitation of 3 requests per second.

please acknowledge such a limitation.


thanks,

gaash
Photo of Gaash Granot

Gaash Granot

  • 206 Points 100 badge 2x thumb

Posted 5 months ago

  • 1
Photo of Tyler Long

Tyler Long, Official Rep

  • 5,554 Points 5k badge 2x thumb
I am unaware of  a limitation of 3 requests per second.

Throttling is per minute: http://ringcentral-api-docs.readthedocs.io/en/latest/rate_limits/

But if you do encounter 429, you need to slow down the api access. Best practice is to write proper code to handle 429 instead of assuming you will never encounter it.

And by the way, there might be multiple instances of your app running so they will share the throttling quota.
(Edited)
Photo of Gaash Granot

Gaash Granot

  • 206 Points 100 badge 2x thumb
thanks.

i already handle 429 cases, but the problem is that i encounter them even when the application doesn't reach the rate limit (i get it when the application has sent only 43-46 calls, when the limit is 50). 
i have only one thread that sends the requests, so it's not a shared resources problem.
(Edited)