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: samples-v2/orchestration_versioning/README.md
+31-1Lines changed: 31 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ What happens to *existing orchestration instances* that were started *before* th
33
33
6. Trigger the external event.
34
34
7. Observe that the orchestration output.
35
35
36
-
```
36
+
```text
37
37
Orchestration version: 1.0
38
38
Suborchestration version: 2.0
39
39
Hello from A!
@@ -42,3 +42,33 @@ Hello from A!
42
42
Note that the value returned by `context.version` is permanently associated with the orchestrator instance and is not impacted by the `defaultVersion` change. As a result, the orchestrator follows the old execution path to guarantee deterministic replay behavior.
43
43
44
44
However, the suborchestration version is `2.0` because this suborchestration was created *after* the `defaultVersion` change.
45
+
46
+
## Overriding Version Programmatically
47
+
48
+
In addition to using `defaultVersion` in `host.json`, you can also specify a version explicitly when starting an orchestration using the `version` parameter of `client.start_new()`:
0 commit comments