Rate limit retry-after not respected

[KimJong]

There seems to be a bug in Fitbit's rate (quantity?) limit system. If a 429 occurs, we grab the `retry-after` from the response header and delay the next fetch until then. However, when we come back to retry we will often receive another 429 with a retry after between 3592-3599 seconds. No, we did not perform 150 requests in that time, this is the very first one for the hour.

So it would seem Fitbit is not respecting it's own `retry-after` value. Looks like we need to hack the retry after value to add 10 seconds or so. Can anyone from Fitbit comment, or can anybody from the community share their solution to this problem? Thanks!

[Gordon-C]

Hi @KimJong 

The rate limit enforcement and reset is approximate.   See https://dev.fitbit.com/build/reference/web-api/developer-guide/application-design/#Rate-Limits.   We are investigating ways to improve the documentation and reset of the rate limit to make it more exact.

Gordon