Merge pull request #311317 from pradeepmi-MSFT/patch-21

(AzureCXP) fixes MicrosoftDocs/azure-docs-pr#550410

Author: prmerger-automator[bot]

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

@@ -23,6 +23,11 @@ Autopurge is enabled by default with a 30 day policy, but it can be customized.
 
 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).
 
+> [!NOTE]
+> 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:
+> - Aren't considered completed or failed for auto-purge purposes.
+> - Aren't removed until they eventually reach a true terminal state (`Completed`, `Failed`, or `Terminated`).
+
 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.
 
 These statuses include: