Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Summary
This article explains how to identify and resolve the TooManyRequestsReceived or SubscriptionRequestsThrottled error (HTTP 429) that occurs when you try to delete an Azure Kubernetes Service (AKS) cluster. Follow the steps in this article to restore successful cluster deletion.
Symptoms
When you try to delete an AKS cluster, you receive the following error message:
internalErrorCode: TooManyRequestsReceived
StatusCode: 429
{
message: "Number of read requests for subscription '.....''' exceeded the limit of '....' for time interval 'XX:XX:XX'. Please try again after '.....' seconds."
}
Cause
Every subscription-level and tenant-level operation is subject to throttling limits. These limits apply to each instance of Azure Resource Manager. When you reach the limit, you receive an HTTP response that indicates status code 429: "Too many requests."
Solution
The HTTP response includes a Retry-After value. This specifies the number of seconds that your application should wait (or sleep) before it sends the next request. If you send a request before the retry value has elapsed, your request isn't processed, and a new retry value is returned. For more information about throttling limits, see Throttling Resource Manager requests.