feat: Avoid hitting rate limits by looking at X-Rate-Limit-* headers
#434
Comments
|
agreed. we are hitting rate warnings on our instance and would love a way to throttle the speed of requests to stay within the api limitation. |
|
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the |
|
Not stale |
|
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the |
|
Not stale |
|
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the |
|
Not stale |
|
Proposal at #450, will wait for feedback before adding docs, tests and updating the template files that generate the code |
|
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the |
|
Not stale |
|
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the |
|
Not stale |
|
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the |
|
Not stale |
|
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the |
|
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the |
|
Thank you for the bump dear stale bot, not stale |
|
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the |
|
Not stale |
|
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the |
|
Not stale |
|
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the |
|
Not stale |
|
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the |
|
Not stale |
|
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the |
|
Not stale |
|
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the |
|
Not stale |
Describe the feature request?
Implement the best practices from https://developer.okta.com/docs/reference/rl-best-practices/#example-rate-limit-header-with-org-wide-rate-limit to avoid hitting rate limits, and also wait until the limit reset time instead of a retry/backoff mechanism.
New or Affected Resource(s)
All existing and new resources will be affected I think
Provide a documentation link
https://developer.okta.com/docs/reference/rl-best-practices/#example-rate-limit-header-with-org-wide-rate-limit
Additional Information?
I'm aware of the existing backoff and retry configuration, it seems better practice to follow the headers returned from the server
The text was updated successfully, but these errors were encountered: