Package io.temporal.api.workflow.v1

Class WorkflowExecutionVersioningInfo.Builder

    • Method Detail

      • getDescriptor

        public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

      • internalGetFieldAccessorTable

        protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
        Specified by:
        internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>

      • getDescriptorForType

        public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
        Specified by:
        getDescriptorForType in interface com.google.protobuf.Message.Builder
        Specified by:
        getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
        Overrides:
        getDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>

      • getDefaultInstanceForType

        public WorkflowExecutionVersioningInfo getDefaultInstanceForType()
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

      • build

        public WorkflowExecutionVersioningInfo build()
        Specified by:
        build in interface com.google.protobuf.Message.Builder
        Specified by:
        build in interface com.google.protobuf.MessageLite.Builder

      • buildPartial

        public WorkflowExecutionVersioningInfo buildPartial()
        Specified by:
        buildPartial in interface com.google.protobuf.Message.Builder
        Specified by:
        buildPartial in interface com.google.protobuf.MessageLite.Builder

      • isInitialized

        public final boolean isInitialized()
        Specified by:
        isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
        Overrides:
        isInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>

      • mergeFrom

        public WorkflowExecutionVersioningInfo.Builder mergeFrom​(com.google.protobuf.CodedInputStream input,
                                                         com.google.protobuf.ExtensionRegistryLite extensionRegistry)
                                                  throws java.io.IOException
        Specified by:
        mergeFrom in interface com.google.protobuf.Message.Builder
        Specified by:
        mergeFrom in interface com.google.protobuf.MessageLite.Builder
        Overrides:
        mergeFrom in class com.google.protobuf.AbstractMessage.Builder<WorkflowExecutionVersioningInfo.Builder>
        Throws:
        java.io.IOException

      • getBehaviorValue

        public int getBehaviorValue()
         Versioning behavior determines how the server should treat this execution when workers are
 upgraded. When present it means this workflow execution is versioned; UNSPECIFIED means
 unversioned. See the comments in `VersioningBehavior` enum for more info about different
 behaviors.
 This field is first set after an execution completes its first workflow task on a versioned
 worker, and set again on completion of every subsequent workflow task.
 For child workflows of Pinned parents, this will be set to Pinned (along with `version`) when
 the the child starts so that child's first workflow task goes to the same Version as the
 parent. After the first workflow task, it depends on the child workflow itself if it wants
 to stay pinned or become unpinned (according to Versioning Behavior set in the worker).
 Note that `behavior` is overridden by `versioning_override` if the latter is present.
        .temporal.api.enums.v1.VersioningBehavior behavior = 1;
        Specified by:
        getBehaviorValue in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        The enum numeric value on the wire for behavior.

      • setBehaviorValue

        public WorkflowExecutionVersioningInfo.Builder setBehaviorValue​(int value)
         Versioning behavior determines how the server should treat this execution when workers are
 upgraded. When present it means this workflow execution is versioned; UNSPECIFIED means
 unversioned. See the comments in `VersioningBehavior` enum for more info about different
 behaviors.
 This field is first set after an execution completes its first workflow task on a versioned
 worker, and set again on completion of every subsequent workflow task.
 For child workflows of Pinned parents, this will be set to Pinned (along with `version`) when
 the the child starts so that child's first workflow task goes to the same Version as the
 parent. After the first workflow task, it depends on the child workflow itself if it wants
 to stay pinned or become unpinned (according to Versioning Behavior set in the worker).
 Note that `behavior` is overridden by `versioning_override` if the latter is present.
        .temporal.api.enums.v1.VersioningBehavior behavior = 1;
        Parameters:
        value - The enum numeric value on the wire for behavior to set.
        Returns:
        This builder for chaining.

      • getBehavior

        public VersioningBehavior getBehavior()
         Versioning behavior determines how the server should treat this execution when workers are
 upgraded. When present it means this workflow execution is versioned; UNSPECIFIED means
 unversioned. See the comments in `VersioningBehavior` enum for more info about different
 behaviors.
 This field is first set after an execution completes its first workflow task on a versioned
 worker, and set again on completion of every subsequent workflow task.
 For child workflows of Pinned parents, this will be set to Pinned (along with `version`) when
 the the child starts so that child's first workflow task goes to the same Version as the
 parent. After the first workflow task, it depends on the child workflow itself if it wants
 to stay pinned or become unpinned (according to Versioning Behavior set in the worker).
 Note that `behavior` is overridden by `versioning_override` if the latter is present.
        .temporal.api.enums.v1.VersioningBehavior behavior = 1;
        Specified by:
        getBehavior in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        The behavior.

      • setBehavior

        public WorkflowExecutionVersioningInfo.Builder setBehavior​(VersioningBehavior value)
         Versioning behavior determines how the server should treat this execution when workers are
 upgraded. When present it means this workflow execution is versioned; UNSPECIFIED means
 unversioned. See the comments in `VersioningBehavior` enum for more info about different
 behaviors.
 This field is first set after an execution completes its first workflow task on a versioned
 worker, and set again on completion of every subsequent workflow task.
 For child workflows of Pinned parents, this will be set to Pinned (along with `version`) when
 the the child starts so that child's first workflow task goes to the same Version as the
 parent. After the first workflow task, it depends on the child workflow itself if it wants
 to stay pinned or become unpinned (according to Versioning Behavior set in the worker).
 Note that `behavior` is overridden by `versioning_override` if the latter is present.
        .temporal.api.enums.v1.VersioningBehavior behavior = 1;
        Parameters:
        value - The behavior to set.
        Returns:
        This builder for chaining.

      • clearBehavior

        public WorkflowExecutionVersioningInfo.Builder clearBehavior()
         Versioning behavior determines how the server should treat this execution when workers are
 upgraded. When present it means this workflow execution is versioned; UNSPECIFIED means
 unversioned. See the comments in `VersioningBehavior` enum for more info about different
 behaviors.
 This field is first set after an execution completes its first workflow task on a versioned
 worker, and set again on completion of every subsequent workflow task.
 For child workflows of Pinned parents, this will be set to Pinned (along with `version`) when
 the the child starts so that child's first workflow task goes to the same Version as the
 parent. After the first workflow task, it depends on the child workflow itself if it wants
 to stay pinned or become unpinned (according to Versioning Behavior set in the worker).
 Note that `behavior` is overridden by `versioning_override` if the latter is present.
        .temporal.api.enums.v1.VersioningBehavior behavior = 1;
        Returns:
        This builder for chaining.

      • hasDeployment

        @Deprecated
public boolean hasDeployment()
        Deprecated.
        temporal.api.workflow.v1.WorkflowExecutionVersioningInfo.deployment is deprecated. See temporal/api/workflow/v1/message.proto;l=159
         The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `version`.
        .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];
        Specified by:
        hasDeployment in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        Whether the deployment field is set.

      • getDeployment

        @Deprecated
public Deployment getDeployment()
        Deprecated.
        temporal.api.workflow.v1.WorkflowExecutionVersioningInfo.deployment is deprecated. See temporal/api/workflow/v1/message.proto;l=159
         The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `version`.
        .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];
        Specified by:
        getDeployment in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        The deployment.

      • setDeployment

        @Deprecated
public WorkflowExecutionVersioningInfo.Builder setDeployment​(Deployment value)
        Deprecated.
         The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `version`.
        .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];

      • setDeployment

        @Deprecated
public WorkflowExecutionVersioningInfo.Builder setDeployment​(Deployment.Builder builderForValue)
        Deprecated.
         The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `version`.
        .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];

      • mergeDeployment

        @Deprecated
public WorkflowExecutionVersioningInfo.Builder mergeDeployment​(Deployment value)
        Deprecated.
         The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `version`.
        .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];

      • clearDeployment

        @Deprecated
public WorkflowExecutionVersioningInfo.Builder clearDeployment()
        Deprecated.
         The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `version`.
        .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];

      • getDeploymentBuilder

        @Deprecated
public Deployment.Builder getDeploymentBuilder()
        Deprecated.
         The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `version`.
        .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];

      • getDeploymentOrBuilder

        @Deprecated
public DeploymentOrBuilder getDeploymentOrBuilder()
        Deprecated.
         The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `version`.
        .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];
        Specified by:
        getDeploymentOrBuilder in interface WorkflowExecutionVersioningInfoOrBuilder

      • getVersion

        public java.lang.String getVersion()
         The Worker Deployment Version that completed the last workflow task of this workflow
 execution, in the form "<deployment_name>.<build_id>".
 Must be present if and only if `behavior` is set. An absent value means no workflow task is
 completed, or the workflow is unversioned.
 For child workflows of Pinned parents, this will be set to parent's Pinned Version when the
 the child starts so that child's first workflow task goes to the same Version as the parent.
 Note that if `versioning_override.behavior` is PINNED then `versioning_override.pinned_version`
 will override this value.
        string version = 5;
        Specified by:
        getVersion in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        The version.

      • getVersionBytes

        public com.google.protobuf.ByteString getVersionBytes()
         The Worker Deployment Version that completed the last workflow task of this workflow
 execution, in the form "<deployment_name>.<build_id>".
 Must be present if and only if `behavior` is set. An absent value means no workflow task is
 completed, or the workflow is unversioned.
 For child workflows of Pinned parents, this will be set to parent's Pinned Version when the
 the child starts so that child's first workflow task goes to the same Version as the parent.
 Note that if `versioning_override.behavior` is PINNED then `versioning_override.pinned_version`
 will override this value.
        string version = 5;
        Specified by:
        getVersionBytes in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        The bytes for version.

      • setVersion

        public WorkflowExecutionVersioningInfo.Builder setVersion​(java.lang.String value)
         The Worker Deployment Version that completed the last workflow task of this workflow
 execution, in the form "<deployment_name>.<build_id>".
 Must be present if and only if `behavior` is set. An absent value means no workflow task is
 completed, or the workflow is unversioned.
 For child workflows of Pinned parents, this will be set to parent's Pinned Version when the
 the child starts so that child's first workflow task goes to the same Version as the parent.
 Note that if `versioning_override.behavior` is PINNED then `versioning_override.pinned_version`
 will override this value.
        string version = 5;
        Parameters:
        value - The version to set.
        Returns:
        This builder for chaining.

      • clearVersion

        public WorkflowExecutionVersioningInfo.Builder clearVersion()
         The Worker Deployment Version that completed the last workflow task of this workflow
 execution, in the form "<deployment_name>.<build_id>".
 Must be present if and only if `behavior` is set. An absent value means no workflow task is
 completed, or the workflow is unversioned.
 For child workflows of Pinned parents, this will be set to parent's Pinned Version when the
 the child starts so that child's first workflow task goes to the same Version as the parent.
 Note that if `versioning_override.behavior` is PINNED then `versioning_override.pinned_version`
 will override this value.
        string version = 5;
        Returns:
        This builder for chaining.

      • setVersionBytes

        public WorkflowExecutionVersioningInfo.Builder setVersionBytes​(com.google.protobuf.ByteString value)
         The Worker Deployment Version that completed the last workflow task of this workflow
 execution, in the form "<deployment_name>.<build_id>".
 Must be present if and only if `behavior` is set. An absent value means no workflow task is
 completed, or the workflow is unversioned.
 For child workflows of Pinned parents, this will be set to parent's Pinned Version when the
 the child starts so that child's first workflow task goes to the same Version as the parent.
 Note that if `versioning_override.behavior` is PINNED then `versioning_override.pinned_version`
 will override this value.
        string version = 5;
        Parameters:
        value - The bytes for version to set.
        Returns:
        This builder for chaining.

      • hasVersioningOverride

        public boolean hasVersioningOverride()
         Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows.
        .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;
        Specified by:
        hasVersioningOverride in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        Whether the versioningOverride field is set.

      • getVersioningOverride

        public VersioningOverride getVersioningOverride()
         Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows.
        .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;
        Specified by:
        getVersioningOverride in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        The versioningOverride.

      • setVersioningOverride

        public WorkflowExecutionVersioningInfo.Builder setVersioningOverride​(VersioningOverride value)
         Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows.
        .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;

      • setVersioningOverride

        public WorkflowExecutionVersioningInfo.Builder setVersioningOverride​(VersioningOverride.Builder builderForValue)
         Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows.
        .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;

      • mergeVersioningOverride

        public WorkflowExecutionVersioningInfo.Builder mergeVersioningOverride​(VersioningOverride value)
         Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows.
        .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;

      • clearVersioningOverride

        public WorkflowExecutionVersioningInfo.Builder clearVersioningOverride()
         Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows.
        .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;

      • getVersioningOverrideBuilder

        public VersioningOverride.Builder getVersioningOverrideBuilder()
         Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows.
        .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;

      • getVersioningOverrideOrBuilder

        public VersioningOverrideOrBuilder getVersioningOverrideOrBuilder()
         Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows.
        .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;
        Specified by:
        getVersioningOverrideOrBuilder in interface WorkflowExecutionVersioningInfoOrBuilder

      • hasDeploymentTransition

        @Deprecated
public boolean hasDeploymentTransition()
        Deprecated.
        temporal.api.workflow.v1.WorkflowExecutionVersioningInfo.deployment_transition is deprecated. See temporal/api/workflow/v1/message.proto;l=193
         When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];
        Specified by:
        hasDeploymentTransition in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        Whether the deploymentTransition field is set.

      • getDeploymentTransition

        @Deprecated
public DeploymentTransition getDeploymentTransition()
        Deprecated.
        temporal.api.workflow.v1.WorkflowExecutionVersioningInfo.deployment_transition is deprecated. See temporal/api/workflow/v1/message.proto;l=193
         When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];
        Specified by:
        getDeploymentTransition in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        The deploymentTransition.

      • setDeploymentTransition

        @Deprecated
public WorkflowExecutionVersioningInfo.Builder setDeploymentTransition​(DeploymentTransition value)
        Deprecated.
         When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];

      • setDeploymentTransition

        @Deprecated
public WorkflowExecutionVersioningInfo.Builder setDeploymentTransition​(DeploymentTransition.Builder builderForValue)
        Deprecated.
         When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];

      • mergeDeploymentTransition

        @Deprecated
public WorkflowExecutionVersioningInfo.Builder mergeDeploymentTransition​(DeploymentTransition value)
        Deprecated.
         When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];

      • clearDeploymentTransition

        @Deprecated
public WorkflowExecutionVersioningInfo.Builder clearDeploymentTransition()
        Deprecated.
         When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];

      • getDeploymentTransitionBuilder

        @Deprecated
public DeploymentTransition.Builder getDeploymentTransitionBuilder()
        Deprecated.
         When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];

      • getDeploymentTransitionOrBuilder

        @Deprecated
public DeploymentTransitionOrBuilder getDeploymentTransitionOrBuilder()
        Deprecated.
         When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];
        Specified by:
        getDeploymentTransitionOrBuilder in interface WorkflowExecutionVersioningInfoOrBuilder

      • hasVersionTransition

        public boolean hasVersionTransition()
         When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
        .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;
        Specified by:
        hasVersionTransition in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        Whether the versionTransition field is set.

      • getVersionTransition

        public DeploymentVersionTransition getVersionTransition()
         When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
        .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;
        Specified by:
        getVersionTransition in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        The versionTransition.

      • setVersionTransition

        public WorkflowExecutionVersioningInfo.Builder setVersionTransition​(DeploymentVersionTransition value)
         When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
        .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;

      • setVersionTransition

        public WorkflowExecutionVersioningInfo.Builder setVersionTransition​(DeploymentVersionTransition.Builder builderForValue)
         When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
        .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;

      • mergeVersionTransition

        public WorkflowExecutionVersioningInfo.Builder mergeVersionTransition​(DeploymentVersionTransition value)
         When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
        .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;

      • clearVersionTransition

        public WorkflowExecutionVersioningInfo.Builder clearVersionTransition()
         When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
        .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;

      • getVersionTransitionBuilder

        public DeploymentVersionTransition.Builder getVersionTransitionBuilder()
         When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
        .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;

      • getVersionTransitionOrBuilder

        public DeploymentVersionTransitionOrBuilder getVersionTransitionOrBuilder()
         When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
        .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;
        Specified by:
        getVersionTransitionOrBuilder in interface WorkflowExecutionVersioningInfoOrBuilder