package temporal.api.errordetails.v1

Get desktop application:
View/edit binary Protocol Buffers messages

An error indicating that an activity execution failed to start. Returned when there is an existing activity with the given activity ID, and the given ID reuse and conflict policies do not permit starting a new one or attaching to an existing one.

• string start_request_id = 1

• string run_id = 2

(message has no fields)

• string client_version = 1

• string client_name = 2

• string supported_versions = 3

• repeated MultiOperationExecutionFailure.OperationStatus statuses = 1

  One status for each requested operation from the failed MultiOperation. The failed operation(s) have the same error details as if it was executed separately. All other operations have the status code `Aborted` and `MultiOperationExecutionAborted` is added to the details field.

NOTE: `OperationStatus` is modelled after [`google.rpc.Status`](https://github.com/googleapis/googleapis/blob/master/google/rpc/status.proto). (-- api-linter: core::0146::any=disabled aip.dev/not-precedent: details are meant to hold arbitrary payloads. --)

Used in: MultiOperationExecutionFailure

• int32 code = 1

• string message = 2

• repeated google.protobuf.Any details = 3

(message has no fields)

• string namespace = 1

• enums.v1.NamespaceState state = 2

  Current state of the requested namespace.

• repeated enums.v1.NamespaceState allowed_states = 3

  Allowed namespace states for requested operation. For example NAMESPACE_STATE_DELETED is forbidden for most operations but allowed for DescribeNamespace.

• string namespace = 1

• string current_cluster = 2

• string active_cluster = 3

• string namespace = 1

NamespaceUnavailableFailure is returned by the service when a request addresses a namespace that is unavailable. For example, when a namespace is in the process of failing over between clusters. This is a transient error that should be automatically retried by clients.

• string namespace = 1

• string default_build_id = 1

  The current default compatible build ID which will receive tasks

An error indicating that a Nexus operation failed to start. Returned when there is an existing operation with the given operation ID, and the given ID reuse and conflict policies do not permit starting a new one or attaching to an existing one.

• string start_request_id = 1

• string run_id = 2

• string current_cluster = 1

• string active_cluster = 2

• string reason = 1

• optional failure.v1.Failure failure = 1

  The full reason for this query failure. May not be available if the response is generated by an old SDK. This field can be encoded by the SDK's failure converter to support E2E encryption of messages and stack traces.

• enums.v1.ResourceExhaustedCause cause = 1

• enums.v1.ResourceExhaustedScope scope = 2

• string server_version = 1

• string client_supported_server_versions = 2

• optional common.v1.WorkflowExecution workflow_execution = 1

  WorkflowId and RunId of the Temporal system workflow performing the underlying operation. Looking up the info of the system workflow run may help identify the issue causing the failure.

• string workflow_error = 2

  Serialized error returned by the system workflow performing the underlying operation.

• string start_request_id = 1

• string run_id = 2

(message has no fields)