Stream Action

Use StreamActions when a client needs to receive Action assignments and lifecycle changes in real time. The stream filters by principals assigned to execute Actions, principals who requested Actions, or principals who authorized Actions.

StreamActions is a server-streaming RPC. For request/response access to Action data, use CreateAction, GetAction, UpdateActionState, and SearchActions.

Stream Filters

The principal filters combine with OR logic. An Action appears if it matches any requested, assigned, or authorized principal filter. The optional source-node filter further constrains results.

Stream Modes

Mode Behavior

ACTION_STREAM_MODE_UNSPECIFIED

Send initial non-terminal Actions, then continue with live updates.

ACTION_STREAM_MODE_INITIAL_ONLY

Send the initial matching queue and close the stream.

ACTION_STREAM_MODE_LIVE_ONLY

Skip initial state and emit only new lifecycle changes.

Event Types

Event Meaning

ACTION_EVENT_TYPE_INITIAL

Action existed when the stream was established.

ACTION_EVENT_TYPE_CREATED

Action was newly created or assigned.

ACTION_EVENT_TYPE_UPDATED

State or progress changed.

ACTION_EVENT_TYPE_CANCELLED

Action was cancelled.

ACTION_EVENT_TYPE_HEARTBEAT

Keepalive message when heartbeat is configured.

Principals that receive Actions on this stream should use Update State to report acknowledgement, planning, execution progress, completion, failure, or cancellation.