Get desktop application:
View/edit binary Protocol Buffers messages
An Update protocol message indicating that a Workflow Update has been accepted (i.e. passed the worker-side validation phase).
Used in:
Headers that are passed with the Update from the requesting entity. These can include things like auth or tracing tokens.
The name of the Update handler to invoke on the target Workflow.
The arguments to pass to the named Update handler.
Metadata about a Workflow Update.
Used in: , ,
An ID with workflow-scoped uniqueness for this Update.
A string identifying the agent that requested this Update.
The outcome of a Workflow Update: success or failure.
Used in: , , ,
An Update protocol message indicating that a Workflow Update has been rejected.
The client request that triggers a Workflow Update.
Used in: , , , , ,
The request ID of the request.
Callbacks to be called by the server when this update reaches a terminal state.
Links to be associated with this update.
An Update protocol message indicating that a Workflow Update has completed with the contained outcome.
The data needed by a client to refer to a previously invoked Workflow Update.
Used in: , ,
Specifies client's intent to wait for Update results.
Used in: ,
Indicates the Update lifecycle stage that the Update must reach before API call is returned. NOTE: This field works together with API call timeout which is limited by server timeout (maximum wait time). If server timeout is expired before user specified timeout, API call returns even if specified stage is not reached.