Skip to content
focoit.com
Back to the canvas

Sequence

The durable reviewer pause

A reviewer step that survives a restart: the pending request is checkpointed and handed back to the reviewer when the workflow is restored.

The durable reviewer pause A sequence across the workflow, a typed review request port, the reviewer UI running as a separate process, and a checkpoint store. The workflow sends a review request to the port, which emits a request event and pauses the workflow while a checkpoint persists the pending request. The process restarts or is redeployed in the middle of the review. On restore, the executor state and pending requests are loaded and the request event is emitted again to the reviewer UI. The reviewer's response, idempotent by request id, is routed back to the workflow, which delivers or refuses, never unreviewed. Workflow executor graph Review request port typed request / response Reviewer UI separate process Checkpoint store durable 1 draft · citations · verdict · versions 2 request event → pause 3 checkpoint at superstep: pending request persisted workflow paused: steady state while a person reviews PROCESS RESTART OR DEPLOY, MID-REVIEW · without a checkpoint the run is lost 4 restore: executor state + pending requests 5 request event emitted again 6 response · edited text · identity idempotent by request id action: accept · edit · reject · escalate → safety reviewer port 7 response routed to the executor Deliver | Refuse: never unreviewed LEGEND Call Return / restore / persist Event (async, one-way) Request port
Reference designOpen full size

What it shows

The review step is a typed request and response port in the workflow, not a polling loop. The workflow sends the draft, its citations, the verdict and the versions; the port emits an event to the reviewer UI, which runs as a separate process, and the workflow pauses.

A checkpoint at each superstep persists the workflow's state and its pending requests. If the process restarts or is redeployed in the middle of a review, the state is restored and the open request is emitted again. The reviewer simply sees it again.

The response carries the edited text and the reviewer's identity, and is idempotent by request id: a double click never delivers twice. The framework routes it back to the step that asked, which delivers or refuses, never unreviewed.

This is a reference design for an agentic clinical-trials Q&A assistant. It is a design, not a description of a system built as shown.

Key decisions

  • Human review is a port in the graph, so the pause is durable for the same reason the rest of the workflow is.
  • Decisions are idempotent by request id.
  • Escalation goes to a second port for a safety reviewer: separation of duties is in the graph.
  • A pending review has a time limit, and an abandoned one is reassigned, never delivered on its own.