Message Store request returning CMN-301 Request rate exceeded despite having 7 as the 'Limit Remaining' returned in the header

  • 1
  • Problem
  • Updated 5 months ago
When making requests on the restapi/v1.0/account/~/extension/{extensionNumber}/message-store" we are receiving CMN-301 Request rate exceeded despite seeing 7 returned as the limit remaining int in the header. 

This also takes into account the 3 requests per second throttle. We wait 0.34 seconds per request to manage it.

Any ideas?

Photo of Snakeboard Snakeboard

Snakeboard Snakeboard

  • 270 Points 250 badge 2x thumb
  • puzzled

Posted 5 months ago

  • 1
Photo of Phong Vu

Phong Vu, Devangelist

  • 5,406 Points 5k badge 2x thumb
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

The 0.34 sec wait time per request is to handle the per second limiter discussed here:

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.
Photo of Tyler Long

Tyler Long, Official Rep

  • 9,818 Points 5k badge 2x thumb
The rate limit is per app per user. Is it because that you have multiple processes running?

We do not have multiple processes running