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
Copy file name to clipboardExpand all lines: articles/storage/blobs/lifecycle-management-overview.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -187,16 +187,14 @@ The run conditions are based on age. Current versions use the last modified time
187
187
188
188
When you add or edit the rules of a lifecycle policy, it can take up to 24 hours for changes to go into effect and for the first execution to start.
189
189
190
-
A policy is scheduled to run once per day (_per 24 hours_) but only if there are no runs in progress. The time required for a run to complete depends on the number of blobs evaluated and operated on. Runs can take longer if the number of requests being made by the policy run along with other workloads reach the request limit of the account. All requests made to storage account, including requests made by policy runs, accrue to the same request limit.
190
+
A policy is scheduled to run once per day (_per 24 hours_) but only if there are no runs in progress.
191
191
192
-
> [!NOTE]
193
-
> For scale limits such as maximum requests rates, see the following articles:
194
-
>
195
-
> -[Scalability and performance targets for Blob storage](scalability-targets.md)
196
-
> -[Scalability and performance targets for standard storage accounts](../common/scalability-targets-standard-account.md)
197
-
> -[Scalability targets for premium block blob storage accounts](scalability-targets-premium-block-blobs.md)
198
-
>
199
-
> To request an increase in account limits, contact [Azure Support](https://azure.microsoft.com/support/faq/).
192
+
The time required for a run to complete depends on the number of blobs evaluated and operated on. Runs can take longer if the number of requests being made per second reaches the request per second limit of the account. All requests made to storage account, including requests made by policy runs, accrue to the same limit on requests per second. To view scale limits, see the following articles:
193
+
-[Scalability and performance targets for Blob storage](scalability-targets.md)
194
+
-[Scalability and performance targets for standard storage accounts](../common/scalability-targets-standard-account.md)
195
+
-[Scalability targets for premium block blob storage accounts](scalability-targets-premium-block-blobs.md)
196
+
197
+
To request an increase in account limits, contact [Azure Support](https://azure.microsoft.com/support/faq/).
200
198
201
199
If a run takes longer than 24 hours to complete, then that run continues without interruption. After the run completes, it is scheduled to run again within 24 hours.
202
200
If you edit, delete, or disable a rule while a run is in progress, then that run terminates within 15 minutes, and runs again within 24 hours. If you disable or delete all of the rules in a policy, then the policy becomes inactive, and no new runs will be scheduled.
0 commit comments