Stream pipeline run status
Opens a Server-Sent Events stream of the run’s status changes. Emits the current status immediately, then each transition, and ends once the run settles (analyzed, failed, or cancelled). Each event’s data is a RunStatusEvent (see the response schema). Authenticate with a Bearer token via a fetch-based client; the native EventSource cannot send an Authorization header.
Path Parameters
URL-safe workspace identifier.
Opaque identifier of the run.
^run_[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$Response
Server-sent event stream; each event's data is the payload below.
A run's status change, broadcast on the core-NATS subject [run_subject].
Fan-out to any watching SSE connections; the run row in Postgres remains the source of truth, so a missed broadcast is recoverable by re-reading the run.
