Skip to content

Commit aa4d3e3

Browse files
Merge pull request #300518 from mumian/0528-arm-throttling
Add Background throttling
2 parents 03e0317 + f7ccc0c commit aa4d3e3

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

articles/azure-resource-manager/management/request-limits-and-throttling.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Understand how Azure Resource Manager throttles requests
33
description: Learn how Azure Resource Manager throttles requests when subscription limits are reached and how to respond.
44
ms.topic: conceptual
5-
ms.date: 01/23/2025
5+
ms.date: 05/28/2025
66
ms.custom: devx-track-arm-template
77
---
88

@@ -49,6 +49,18 @@ Since different regions have a different number of Resource Manager instances, t
4949

5050
You can send more requests. Write requests increase by 30 times. Delete requests increase by 2.4 times. Read requests increase by 7.5 times.
5151

52+
## Background Job Throttling
53+
54+
Background jobs in Azure Resource Manager (ARM) are automated tasks that run behind the scenes to support operations such as resource deployments, diagnostics, and system maintenance. These jobs are essential for processing user requests and ensuring service functionality. To maintain platform stability and reliability, ARM employs background job throttling to manage the load from these tasks.
55+
56+
You can identify when background job throttling occurs if you receive the following error message:
57+
58+
```error
59+
The request for subscription '{0}' could not be processed due to an excessive volume of traffic. Please try again later.
60+
```
61+
62+
Customers might experience throttling due to excessive background jobs, which can be triggered by high-frequency operations or system-wide activities. While customers do not have direct control over the creation or execution of these jobs, awareness of potential throttling is important.
63+
5264
## Throttling for non-public clouds
5365

5466
Throttling happens at two levels. Azure Resource Manager throttles requests for the subscription and tenant. If the request is under the throttling limits for the subscription and tenant, Resource Manager routes the request to the resource provider. The resource provider applies throttling limits that are tailored to its operations.

0 commit comments

Comments
 (0)