Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
Used in:
next_retry_delay can be used by the client to override the activity retry interval calculated by the retry policy. Retry attempts will still be subject to the maximum retries limit and total time limit defined by the policy.
Used in:
The identity of the worker or client that requested the cancellation.
Used in:
Used in: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
The source this Failure originated in, e.g. TypeScriptSDK / JavaSDK In some SDKs this is used to rehydrate the stack trace into an exception object.
Alternative way to supply `message` and `stack_trace` and possibly other attributes, used for encryption of errors originating in user code which might contain sensitive information. The `encoded_attributes` Payload could represent any serializable object, e.g. JSON object or a `Failure` proto message. SDK authors: - The SDK should provide a default `encodeFailureAttributes` and `decodeFailureAttributes` implementation that: - Uses a JSON object to represent `{ message, stack_trace }`. - Overwrites the original message with "Encoded failure" to indicate that more information could be extracted. - Overwrites the original stack_trace with an empty string. - The resulting JSON object is converted to Payload using the default PayloadConverter and should be processed by the user-provided PayloadCodec - If there's demand, we could allow overriding the default SDK implementation to encode other opaque Failure attributes. (-- api-linter: core::0203::optional=disabled --)
(message has no fields)
Used in:
The Nexus error type as defined in the spec: https://github.com/nexus-rpc/api/blob/main/SPEC.md#predefined-handler-errors.
Retry behavior, defaults to the retry behavior of the error type as defined in the spec.
Representation of the Temporal SDK NexusOperationError object that is returned to workflow callers.
Used in:
The NexusOperationScheduled event ID.
Endpoint name.
Service name.
Operation name.
Operation ID - may be empty if the operation completed synchronously. Deprecated. Renamed to operation_token.
Operation token - may be empty if the operation completed synchronously.
Used in:
Used in:
Used in:
The identity of the worker or client that requested the termination.
Used in: