You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been hearing your asks for higher hourly request limits and are happy to announce that as of today, the hourly request limit has been raised from 20,000 requests/hour to 30,000 requests/hour in the standard tier. Additionally, when the hourly limit is reached, some requests may return the HTTP status code 429 until the end of that hour. As more requests exceed the limit, more requests may return HTTP status code 429.
This change avoids a hard cutoff for applications that have hit the request limit. You can monitor an App Configuration store’s request count and follow these best practices to reduce requests made.
If you have any questions or feedback on this change, you can open an issue in our Github repo.
The text was updated successfully, but these errors were encountered:
Azure
locked as resolved and limited conversation to collaborators
Aug 20, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have been hearing your asks for higher hourly request limits and are happy to announce that as of today, the hourly request limit has been raised from 20,000 requests/hour to 30,000 requests/hour in the standard tier. Additionally, when the hourly limit is reached, some requests may return the HTTP status code 429 until the end of that hour. As more requests exceed the limit, more requests may return HTTP status code 429.
This change avoids a hard cutoff for applications that have hit the request limit. You can monitor an App Configuration store’s request count and follow these best practices to reduce requests made.
If you have any questions or feedback on this change, you can open an issue in our Github repo.
The text was updated successfully, but these errors were encountered: