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/azure-functions/durable-task-scheduler/durable-task-scheduler-auto-purge.md
+13-10Lines changed: 13 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.date: 04/28/2025
7
7
8
8
# Set autopurge retention policies for Azure Functions Durable Task Scheduler (preview)
9
9
10
-
Orchestration history data should be purged periodically to free up storage resources. Otherwise, the app will likely observe performance degradation as history data accumulates overtime. The Durable Task Scheduler offers a lightweight, configurable autopurge feature that helps you manage orchestration data clean-up without manual intervention.
10
+
Orchestration history data should be purged periodically to free up storage resources. Otherwise, the app observes performance degradation as history data accumulates overtime. The Durable Task Scheduler offers a lightweight, configurable autopurge feature that helps you manage orchestration data clean-up without manual intervention.
11
11
12
12
Autopurge operates asynchronously in the background, optimized to minimize system resource usage and prevent interference with other Durable Task operations. Although autopurge doesn't adhere to a strict schedule, its clean-up rate generally aligns with your orchestration scheduling rate.
13
13
@@ -55,7 +55,7 @@ When configuring an autopurge retention policy, you can set either a *specific*
55
55
}
56
56
```
57
57
58
-
Add specific policies to override the default policy applied to orchestrations, regardless of status. In the example below, the second and third policies override the default policy (`"retentionPeriodInDays": 1`).
58
+
Add specific policies to override the default policy applied to orchestrations, regardless of status. In the following example, the second and third policies override the default policy (`"retentionPeriodInDays": 1`).
59
59
- Data associated with completed orchestrations is deleted immediately.
60
60
- Data associated with failed orchestrations is purged after 60 days.
61
61
@@ -141,7 +141,7 @@ PUT https://management.azure.com/subscriptions/SUBSCRIPTION_ID/resourceGroups/RE
141
141
142
142
**Example response**
143
143
144
-
If creation is successful, you'll see the following response.
144
+
If creation is successful, you receive the following response.
145
145
146
146
```json
147
147
{
@@ -177,7 +177,7 @@ If creation is successful, you'll see the following response.
177
177
178
178
# [Azure CLI](#tab/cli)
179
179
180
-
Create or update the retention policy by running the following:
180
+
Create or update the retention policy by running the following command.
181
181
182
182
```azurecli
183
183
az rest --method put --url "/subscriptions/SUBSCRIPTION_ID/resourceGroups/RESOURCE_GROUP/providers/Microsoft.DurableTask/schedulers/SCHEDULER_NAME/retentionPolicies/default?api-version=2025-04-01-preview" --body '{
@@ -203,7 +203,7 @@ Create or update the retention policy by running the following:
203
203
204
204
**Example response**
205
205
206
-
If creation is successful, you'll see the following response.
206
+
If creation is successful, you receive the following response.
207
207
208
208
```json
209
209
{
@@ -240,23 +240,26 @@ If creation is successful, you'll see the following response.
0 commit comments