When the reservoir is not the same as x-ratelimit-remaining it causes a error.
It happens when the api has been used by something else or x-ratelimit-remaining is not set to the max when it is started.
Is there a way I can tell the module the response header x-ratelimit-remaining so it does not happen?
When the reservoir is not the same as x-ratelimit-remaining it causes a error. It happens when the api has been used by something else or x-ratelimit-remaining is not set to the max when it is started. Is there a way I can tell the module the response header x-ratelimit-remaining so it does not happen?