Get desktop application:
View/edit binary Protocol Buffers messages
A request to cancel an operation.
Used in:
Service name.
Type of operation to cancel.
Operation ID as originally generated by a Handler. Deprecated. Renamed to operation_token.
Operation token as originally generated by a Handler.
Response variant for CancelOperationRequest.
Used in:
(message has no fields)
A cluster-global binding from an endpoint ID to a target for dispatching incoming Nexus requests.
Used in: , , ,
Data version for this endpoint, incremented for every update issued via the UpdateNexusEndpoint API.
Unique server-generated endpoint ID.
Spec for the endpoint.
The date and time when the endpoint was created. (-- api-linter: core::0142::time-field-names=disabled aip.dev/not-precedent: Not following linter rules. --)
The date and time when the endpoint was last modified. Will not be set if the endpoint has never been modified. (-- api-linter: core::0142::time-field-names=disabled aip.dev/not-precedent: Not following linter rules. --)
Server exposed URL prefix for invocation of operations on this endpoint. This doesn't include the protocol, hostname or port as the server does not know how it should be accessed publicly. The URL is stable in the face of endpoint renames.
Contains mutable fields for an Endpoint.
Used in: , ,
Endpoint name, unique for this cluster. Must match `[a-zA-Z_][a-zA-Z0-9_]*`. Renaming an endpoint breaks all workflow callers that reference this endpoint, causing operations to fail.
Markdown description serialized as a single JSON string. If the Payload is encrypted, the UI and CLI may decrypt with the configured codec server endpoint. By default, the server enforces a limit of 20,000 bytes for this entire payload.
Target to route requests to.
Target to route requests to.
Used in:
Target an external server by URL. At a later point, this will support providing credentials, in the meantime, an http.RoundTripper can be injected into the server to modify the request.
Used in:
URL to call.
Target a worker polling on a Nexus task queue in a specific namespace.
Used in:
Namespace to route requests to.
Nexus task queue to route requests to.
A general purpose failure message. See: https://github.com/nexus-rpc/api/blob/main/SPEC.md#failure
Used in: ,
UTF-8 encoded JSON serializable details.
Used in:
See 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.
Used in: , ,
See https://github.com/nexus-rpc/api/blob/main/SPEC.md#links.
NexusOperationExecutionCancellationInfo contains the state of a Nexus operation cancellation.
Used in:
The time when cancellation was requested.
The number of attempts made to deliver the cancel operation request. This number represents a minimum bound since the attempt is incremented after the request completes.
The time when the last attempt completed.
The last attempt's failure, if any.
The time when the next attempt is scheduled.
If the state is BLOCKED, blocked reason provides additional information.
A reason that may be specified in the CancelNexusOperationRequest.
Full current state of a standalone Nexus operation, as of the time of the request.
Used in:
Unique identifier of this Nexus operation within its namespace along with run ID (below).
Endpoint name, resolved to a URL via the cluster's endpoint registry.
Service name.
Operation name.
A general status for this operation, indicates whether it is currently running or in one of the terminal statuses. Updated once when the operation is originally scheduled, and again when it reaches a terminal status.
More detailed breakdown of NEXUS_OPERATION_EXECUTION_STATUS_RUNNING.
Schedule-to-close timeout for this operation. (-- api-linter: core::0140::prepositions=disabled aip.dev/not-precedent: "to" is used to indicate interval. --)
Schedule-to-start timeout for this operation. (-- api-linter: core::0140::prepositions=disabled aip.dev/not-precedent: "to" is used to indicate interval. --)
Start-to-close timeout for this operation. (-- api-linter: core::0140::prepositions=disabled aip.dev/not-precedent: "to" is used to indicate interval. --)
The number of attempts made to deliver the start operation request. This number is approximate, it is incremented when a task is added to the history queue. In practice, there could be more attempts if a task is executed but fails to commit, or less attempts if a task was never executed.
Time the operation was originally scheduled via a StartNexusOperation request.
Scheduled time + schedule to close timeout.
Time when the operation transitioned to a closed state.
The time when the last attempt completed.
The last attempt's failure, if any.
The time when the next attempt is scheduled.
Elapsed time from schedule_time to now for running operations or to close_time for closed operations, including all attempts and backoff between attempts.
If the state is BLOCKED, blocked reason provides additional information.
Server-generated request ID used as an idempotency token when submitting start requests to the handler. Distinct from the request_id in StartNexusOperationRequest, which is the caller-side idempotency key for the StartNexusOperation RPC itself.
Operation token. Only set for asynchronous operations after a successful StartOperation call.
Incremented each time the operation's state is mutated in persistence.
Header for context propagation and tracing purposes.
Metadata for use by user interfaces to display the fixed as-of-start summary and details of the operation.
Links attached by the handler of this operation on start or completion.
The identity of the client who started this operation.
Updated once on scheduled and once on terminal status.
Limited Nexus operation information returned in the list response. When adding fields here, ensure that it is also present in NexusOperationExecutionInfo (note that it may already be present in NexusOperationExecutionInfo but not at the top-level).
Used in:
A unique identifier of this operation within its namespace along with run ID (below).
The run ID of the standalone Nexus operation.
Endpoint name.
Service name.
Operation name.
Time the operation was originally scheduled via a StartNexusOperation request.
If the operation is in a terminal status, this field represents the time the operation transitioned to that status.
The status is updated once, when the operation is originally scheduled, and again when the operation reaches a terminal status.
Search attributes from the start request.
Updated on terminal status.
The difference between close time and scheduled time. This field is only populated if the operation is closed.
Updated once on scheduled and once on terminal status.
A Nexus request.
Used in:
Headers extracted from the original request in the Temporal frontend. When using Nexus over HTTP, this includes the request's HTTP headers ignoring multiple values.
The timestamp when the request was scheduled in the frontend. (-- api-linter: core::0142::time-field-names=disabled aip.dev/not-precedent: Not following linter rules. --)
The endpoint this request was addressed to before forwarding to the worker. Supported from server version 1.30.0.
Used in:
If set, handlers may use temporal.api.failure.v1.Failure instances to return failures to the server. This also allows handler and operation errors to have their own messages and stack traces.
A response indicating that the handler has successfully processed a request.
Used in:
Variant must correlate to the corresponding Request's variant.
A request to start an operation.
Used in:
Name of service to start the operation in.
Type of operation to start.
A request ID that can be used as an idempotentency key.
Callback URL to call upon completion if the started operation is async.
Full request body from the incoming HTTP request.
Header that is expected to be attached to the callback request when the operation completes.
Links contain caller information and can be attached to the operations started by the handler.
Response variant for StartOperationRequest.
Used in:
The operation completed unsuccessfully (failed or canceled). Deprecated. Use the failure variant instead.
The operation completed unsuccessfully (failed or canceled). Failure object must contain an ApplicationFailureInfo or CanceledFailureInfo object.
The operation will complete asynchronously. The returned ID can be used to reference this operation.
Used in:
Deprecated. Renamed to operation_token.
An operation completed successfully.
Used in:
Used in:
See https://github.com/nexus-rpc/api/blob/main/SPEC.md#operationinfo.