Durable execution records enough state and event history to resume after crashes without losing progress or duplicating effects. Persistence boundaries belong in graph semantics, not only infrastructure.

Durable Execution Survives Process Failure

Observability correlates traces, metrics, logs, prompts, models, graph versions, and user outcomes. It should answer which path ran and why without collecting unnecessary content.

Graph Observability Connects Runs to Design

Persisted state outlives code versions. A schema migration must transform old checkpoints deterministically, preserve invariants, and support rollback or quarantine when conversion fails.

Graph State Needs Versioned Migration

An idempotent operation can be retried with the same key without multiplying its intended effect. It is essential when acknowledgements can be lost after an action succeeds.

Idempotency Makes Repetition Safe

In this situation—resuming a multi-hour document review after a deployment—which choice best applies “Durable Execution Survives Process Failure”?

A timeout limits waiting, while cancellation asks downstream work to stop and release resources. The graph must define whether late results are ignored, compensated, or still valid.

Learn Before

Related