|
| 1 | +--- |
| 2 | +title: Troubleshoot the Throttled Error Code (429) |
| 3 | +description: Learn how to resolve the Throttled error (status 429) when you try to create and deploy an Azure Kubernetes Service (AKS) cluster. |
| 4 | +ms.date: 03/05/2025 |
| 5 | +ms.reviewer: jovieir, chiragpa, v-weizhu |
| 6 | +ms.service: azure-kubernetes-service |
| 7 | +#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the Throttled error code (status 429) so that I can successfully create and deploy an Azure Kubernetes Service (AKS) cluster. |
| 8 | +ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool) |
| 9 | +--- |
| 10 | +# Troubleshoot the Throttled error code (429) |
| 11 | + |
| 12 | +This article discusses how to identify and resolve the `Throttled` error (status 429) that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster. |
| 13 | + |
| 14 | +## Symptoms |
| 15 | + |
| 16 | +When you try to create an AKS cluster, you receive the following "The PutManagedClusterHandler.PUT request limit has been exceeded" error message that shows a "SubCode" value of **Throttled** and a "Status" value of **429**: |
| 17 | + |
| 18 | +> Category: ClientError; |
| 19 | +> |
| 20 | +> SubCode: Throttled; |
| 21 | +> |
| 22 | +> OrginalError: autorest/azure: Service returned an error. **Status=429** |
| 23 | +> |
| 24 | +> **Code="Throttled"** |
| 25 | +> |
| 26 | +> Message="> The PutManagedClusterHandler.PUT request limit has been exceeded for SubID='*\<subscription-id-guid>*', please retry again in X seconds. For more information, please visit aka.ms/aks/throttling"; |
| 27 | +Request throttling can occur on various Azure components, so the error message might be different depending on the type of resource where this issue occurs. |
| 28 | + |
| 29 | +Resource provider throttling is independent of ARM throttling and is tailored to the operations of a specific resource provider. In this scenario, AKS resource provider throttling is specific to the AKS resource provider and applies only to operations related to AKS resources. |
| 30 | + |
| 31 | +## Cause |
| 32 | + |
| 33 | +AKS requests are throttled. For information about how AKS limits work and the specific limits per hour, see [Throttling limits on AKS resource provider APIs](/azure/aks/quotas-skus-regions#throttling-limits-on-aks-resource-provider-apis). |
| 34 | + |
| 35 | +## Solution |
| 36 | + |
| 37 | +To resolve this issue, examine and modify your access pattern of the throttled subscription. The following table lists the possible access patterns and corresponding solutions. |
| 38 | + |
| 39 | +| Access pattern | Solution | |
| 40 | +| -------------- | -------- | |
| 41 | +| Automated scripts constantly run LIST operations against managedCluster resources. | Run the scripts less frequently. | |
| 42 | +| Users attempt to deploy multiple AKS clusters in a short period of time. | Space out deployments or use different subscriptions.| |
| 43 | +| Users attempt to modify the same AKS cluster multiple times consecutively. | Space out operations. Ensure successful completion before initiating another one.| |
| 44 | +| Users attempt to add, modify, or delete one or more agentPools on the same AKS cluster. | Space out operations. Ensure successful completion before initiating another one. | |
| 45 | + |
| 46 | +## More information |
| 47 | + |
| 48 | +[General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md) |
| 49 | + |
| 50 | +[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)] |
0 commit comments