Experimental. Optionally decide the versioning behavior that the first task of the new run should use. For example, choose to AutoUpgrade on continue-as-new instead of inheriting the pinned version of the previous run.
| Constant | AUTO |
Start the new run with AutoUpgrade behavior. Use the Target Version of the workflow's task queue at start-time, as AutoUpgrade workflows do. After the first workflow task completes, use whatever Versioning Behavior the workflow is annotated with in the workflow code. |
| Constant | UNSPECIFIED |
An initial versioning behavior is not set, follow the existing continue-as-new inheritance semantics. See https://docs.temporal.io/worker-versioning#inheritance-semantics for more detail. |
Start the new run with AutoUpgrade behavior. Use the Target Version of the workflow's task queue at start-time, as AutoUpgrade workflows do. After the first workflow task completes, use whatever Versioning Behavior the workflow is annotated with in the workflow code.
Note that if the previous workflow had a Pinned override, that override will be inherited by the new workflow run regardless of the ContinueAsNewVersioningBehavior specified in the continue-as-new command. If a Pinned override is inherited by the new run, and the new run starts with AutoUpgrade behavior, the base version of the new run will be the Target Version as described above, but the effective version will be whatever is specified by the Versioning Override until the override is removed.
| Value |
|
An initial versioning behavior is not set, follow the existing continue-as-new inheritance semantics. See https://docs.temporal.io/worker-versioning#inheritance-semantics for more detail.
| Value |
|