NikaRunEvent is open to additive fields and event kinds. Render only what
the application understands, preserve the sequence, and use run.result()
for terminal truth. The untouched protocol frame is on event.raw.
A nika serve 0.124.3 job streams two lifecycle events: run.started
(execution.started), then run.settled (execution.settled, or
execution.cancelled / execution.refused) or run.waiting for a paused
job. A job admitted with a non-empty inputs map first records
execution.queued (sequence 1), which arrives as an engine.event. There
are no per-task events over HTTP, and the SDK never invents one; read
run.status() for the current state between them.
Run events maps every
kind on both transports.
Each subscriber has a bounded queue. If a consumer falls behind, the SDK
throws NikaEventBufferOverflowError rather than silently losing evidence.
Stop one view
run.cancel() to ask the
server to cancel engine work.
Resume from application state
paused settlement closes the stream and resolves run.result() with
status: 'paused'. In 0.124.3 the server has no route to answer the gate, so
the job stays paused (Jobs).
Replaying or attaching after the settlement event was consumed still reads
the full stored settlement. Stopping a stream or attaching to a job never
answers a human gate.
Which published source this page describes
Which published source this page describes
Jobs
Own identity and recovery around the stream.
Runtime events
Build a tolerant presentation reducer.