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/durable-task-scheduler/durable-task-scheduler-versioning.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.author: azfuncdf
8
8
zone_pivot_groups: df-languages
9
9
---
10
10
11
-
# Orchestration Versioning
11
+
# Orchestration Versioning (preview)
12
12
13
13
A key area to consider when using a durable orchestration system is how to handle the upgrading/downgrading of orchestrations. When an orchestration is interrupted and later resumed (for instance, during a host update), Durable Task Scheduler will replay the events of the orchestration. This is done to ensure reliability - the system replays to ensure all previous steps were executed successfully before the next step is taken - which is a core promise of the durable execution paradigm. So, if an orchestration changes between deployments, the steps it takes may no longer be the same. If this does happen, the system will throw a `NonDeterministicError` instead of allowing the orchestration to continue.
14
14
@@ -44,7 +44,7 @@ In order for an orchestration to have a version, it must first be set in the cli
44
44
::: zone pivot="csharp"
45
45
46
46
> [!NOTE]
47
-
> Available in the .NET SDK since v1.9.0.
47
+
> Available in the .NET SDK (Microsoft.DurableTask.Client.AzureManaged) since v1.9.0.
0 commit comments