I am not sure about the limit remaining in the header. But within the light limit group, you can send 50 requests per 60 seconds. That makes about 1.2 secs per request. Therefore, waiting for 0.34 sec to send each request will cause throttling.
+ Phong
Hello,
The 0.34 sec wait time per request is to handle the per second limiter discussed here:
https://devcommunity.ringcentral.com/ringcentraldev/topics/ringcentral-csharp-handling-429-exception...It is to not designed to manage the 50 requests per minute on the light limit group.
It appears that the header X-Rate-Limit-Remaining is invalid.
Should the solution not use this value to handle the request throttling? It is used throughout the application for different end points and it doesn't seem to have this issue.
For example the endpoint: restapi/v1.0/account/~/call-log uses the exact same architecture where the limiter inspects the remaining header and if it's 0 it waits 60 seconds and continues normally.
