Skip to content

resume.md

Latest commit

 

History

History
37 lines (25 loc) · 1.18 KB

resume.md

File metadata and controls

37 lines (25 loc) · 1.18 KB
Raw

Resume (§6.3)

Resume lets a client recover events after a transport drop. The Rust SDK stores events in EventLog and can replay by session and event sequence.

Spec reference: §6.3.

What to persist

Clients should persist:

  • session_id
  • resume token or runtime-specific resume credential
  • highest processed event_seq

The runtime must retain events for the session until the resume window expires. Use a file-backed event log when reconnect must survive runtime restarts.

Replay

On resume, the runtime sends events with event_seq > last_event_seq. Sequence numbers are session-scoped, so one high-water mark covers every job in the session.

Example

examples/resumability/ demonstrates replaying events after a session boundary.

Failure modes

  • DATA_LOSS means the runtime no longer has the buffered history needed to serve the requested event_seq (retention swept).
  • INVALID_ARGUMENT means the resume tuple is malformed or claims an impossible sequence boundary.
  • An in-memory event log loses resume history on restart; use a file-backed log for restart-tolerant resume.