Stream Storage Events
Stream storage write events via Server-Sent Events.
Pipeline adapters write content to storage during execution. Each write
emits a storage.object.created event on /topic/system.storage.events.
This endpoint subscribes to the topic, filters by execution/stage/path/extension,
and streams matching events to the client.
Multi-execution aggregation: pass execution_id multiple times
(?execution_id=tag1&execution_id=tag2) to multiplex events from several
executions in a single stream. Each event carries its execution_id so
consumers can distinguish sources.
Resumable: set the Last-Event-ID request header to skip events that
sort lexicographically ≤ the provided UUIDv7. Best-effort — events
published during the reconnect gap are lost.
The stream ends when all watched executions reach terminal state (completed/failed/cancelled), the timeout is reached, or the client disconnects.
Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”Execution UUID or tag(s); repeat for multi-execution watch
Execution UUID or tag(s); repeat for multi-execution watch
Stream timeout in seconds
Stream timeout in seconds
Do not auto-terminate when all watched executions complete
Do not auto-terminate when all watched executions complete
Responses
Section titled “ Responses ”Successful Response
Resource not found
Standard error response matching FastAPI HTTPException format.
This model is used in OpenAPI response declarations for 4xx/5xx errors.
The detail field matches FastAPI’s HTTPException structure.
Validation Error
object
object
object
Storage event streamer not available
Standard error response matching FastAPI HTTPException format.
This model is used in OpenAPI response declarations for 4xx/5xx errors.
The detail field matches FastAPI’s HTTPException structure.