Table of Contents

Namespace Temporalio.Api.Enums.V1

Classes

BatchOperationReflection

Holder for reflection information generated from temporal/api/enums/v1/batch_operation.proto

CommandTypeReflection

Holder for reflection information generated from temporal/api/enums/v1/command_type.proto

CommonReflection

Holder for reflection information generated from temporal/api/enums/v1/common.proto

EventTypeReflection

Holder for reflection information generated from temporal/api/enums/v1/event_type.proto

FailedCauseReflection

Holder for reflection information generated from temporal/api/enums/v1/failed_cause.proto

NamespaceReflection

Holder for reflection information generated from temporal/api/enums/v1/namespace.proto

QueryReflection

Holder for reflection information generated from temporal/api/enums/v1/query.proto

ResetReflection

Holder for reflection information generated from temporal/api/enums/v1/reset.proto

ScheduleReflection

Holder for reflection information generated from temporal/api/enums/v1/schedule.proto

TaskQueueReflection

Holder for reflection information generated from temporal/api/enums/v1/task_queue.proto

UpdateReflection

Holder for reflection information generated from temporal/api/enums/v1/update.proto

WorkflowReflection

Holder for reflection information generated from temporal/api/enums/v1/workflow.proto

Enums

ArchivalState
BatchOperationState
BatchOperationType
CancelExternalWorkflowExecutionFailedCause
CommandType

Whenever this list of command types is changed do change the function shouldBufferEvent in mutableStateBuilder.go to make sure to do the correct event ordering.

ContinueAsNewInitiator
EncodingType
EventType

Whenever this list of events is changed do change the function shouldBufferEvent in mutableStateBuilder.go to make sure to do the correct event ordering

HistoryEventFilterType
IndexedValueType
NamespaceState
ParentClosePolicy

Defines how child workflows will react to their parent completing

PendingActivityState
PendingWorkflowTaskState
QueryRejectCondition
QueryResultType
ReplicationState
ResetReapplyExcludeType

Event types to exclude when reapplying events.

ResetReapplyType

Event types to include when reapplying events. Deprecated: applications should use ResetReapplyExcludeType to specify exclusions from this set, and new event types should be added to ResetReapplyExcludeType instead of here.

ResetType

Reset type options. Deprecated, see temporal.api.common.v1.ResetOptions.

ResourceExhaustedCause
RetryState
ScheduleOverlapPolicy

ScheduleOverlapPolicy controls what happens when a workflow would be started by a schedule, and is already running.

Severity
SignalExternalWorkflowExecutionFailedCause
StartChildWorkflowExecutionFailedCause
TaskQueueKind
TaskQueueType
TaskReachability

Specifies which category of tasks may reach a worker on a versioned task queue. Used both in a reachability query and its response.

TimeoutType
UpdateRequestedEventOrigin

UpdateRequestedEventOrigin records why an WorkflowExecutionUpdateRequestedEvent was written to history. Note that not all update requests result in a WorkflowExecutionUpdateRequestedEvent.

UpdateWorkflowExecutionLifecycleStage

UpdateWorkflowExecutionLifecycleStage is specified by clients invoking workflow execution updates and used to indicate to the server how long the client wishes to wait for a return value from the RPC. If any value other than UPDATE_WORKFLOW_EXECUTION_LIFECYCLE_STAGE_COMPLETED is sent by the client then the RPC will complete before the update is finished and will return a handle to the running update so that it can later be polled for completion.

WorkflowExecutionStatus

(-- api-linter: core::0216::synonyms=disabled aip.dev/not-precedent: There is WorkflowExecutionState already in another package. --)

WorkflowIdReusePolicy

Defines how new runs of a workflow with a particular ID may or may not be allowed. Note that it is never valid to have two actively running instances of the same workflow id.

WorkflowTaskFailedCause

Workflow tasks can fail for various reasons. Note that some of these reasons can only originate from the server, and some of them can only originate from the SDK/worker.