Skip to content

Commit 75de33f

Browse files
Update articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-auto-purge.md
Co-authored-by: Hannah Hunter <[email protected]>
1 parent 8b40fb4 commit 75de33f

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-auto-purge.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,9 @@ Autopurge is an opt-in feature. You can enable it by defining retention policies
2222
The orchestration instances eligible for autopurge match those targeted by [the Durable SDK PurgeInstancesAsync API](/dotnet/api/microsoft.durabletask.client.durabletaskclientextensions.purgeinstancesasync?view=durabletask-dotnet-1.x&preserve-view=true).
2323

2424
>[!Note]
25-
>Orchestrations that use ContinueAsNew may appear with a status that is marked as obsolete in some C# SDK versions. This is expected behavior. ContinueAsNew does not represent a terminal state. Instead, it restarts the orchestration with a new execution history while preserving the instance ID. Because of this, such instances are not considered completed or failed for auto-purge purposes and will not be removed until they eventually reach a true terminal state (Completed, Failed, or Terminated).
25+
> Orchestrations using `ContinueAsNew` may appear with a status that is marked as obsolete in some C# SDK versions. This behavior is expected. `ContinueAsNew` does not represent a terminal state. Instead, it restarts the orchestration with a new execution history while preserving the instance ID. In this case, such instances:
26+
> - Aren't considered completed or failed for auto-purge purposes.
27+
> - Aren't removed until they eventually reach a true terminal state (`Completed`, `Failed`, or `Terminated`).
2628
2729
Autopurge ignores orchestration data associated with non-terminal statuses. "Non-terminal" statuses indicate that the orchestration instance is either actively executing, paused, or in a state where it may resume in the future (waiting for external events or timers). These orchestrations that are continuing as new, where the current *execution* is completed, but a new instance has been started as a continuation.
2830

0 commit comments

Comments
 (0)