The outcome

Resume long-running agents after failure without silently duplicating side effects or accepting regressions in behavior.

Step by step

A workflow you can repeat.

  1. 01

    Select Temporal, DBOS, Prefect, Restate, or another documented integration by runtime needs, then define durable units, stable IDs, determinism, retention, retries, approvals, and recovery objectives.

  2. 02

    Pin the agent and toolset identities, move nondeterministic I/O into checkpointed activities or tasks, use idempotency keys for effects, and encrypt state and credentials with least privilege.

  3. 03

    Create a versioned eval dataset covering final outputs and tool trajectories, deterministic invariants, safety, permissions, cost, and known failure examples from development and production.

  4. 04

    Test worker crash, provider timeout, retry, replay, changed code, duplicate effect, toolset-ID collision, long pause, cancellation, key rotation, migration, and the integration's documented limitations.

  5. 05

    Gate releases on eval and recovery thresholds, compare traces with production, canary workflow versions, retain compatible workers and rollback, and rehearse state deletion and incident response.

Working standard

What good use looks like.

  • Give durable toolsets stable IDs.
  • Checkpoint nondeterministic operations.
  • Evaluate trajectories, not only answers.

Official references

Check the current product documentation.