Checkpoint

Step · Stable

Wait until several conditions are met (all or any), with a timeout.

A synchronization gate: the run pauses until ALL (policy: all) or ANY (policy: any) of a list of conditions are satisfied. Each condition is an event (a platform event fires), a signal (an actor approves / replies), or a timer (a relative delay elapses). A timeout is MANDATORY — when it elapses the run CONTINUES (it does not fail), exposing {{ .reason }} == ‘timed_out’ so downstream steps can react. Stored as a Wait step with a conditions list — the multi-condition form of Wait surfaced as its own node.

Joining fire-and-continue asks: add a signal condition with from_step: . The Checkpoint then subscribes to the signal that ask created instead of opening a fresh one. Each satisfied response is exposed under the Checkpoint’s label keyed by the condition’s key — {{ <wait_label>.<condition_key> }} returns the actor reply.

When to use

Use when you need to join multiple independent signals before the flow continues — e.g. wait for BOTH a manager approval AND a finance sign-off, or proceed as soon as EITHER arrives. Also the required join node for fire-and-continue Ask Actor fan-outs: each upstream ask adds one signal condition here.

When not to use

For a single pause (one delay or one event), use Wait — Checkpoint adds complexity that is only justified by multiple conditions. For simple yes/no routing after a single Ask Actor, a Branch is cleaner.

Inputs

Configured per use: conditions, policy, timeout.

---

Auto-generated from the skill registry (load_skills()). Do not edit by hand.