Persistence recovery

Explore conflicts, lost responses and partial saves using the real editor runtime.

Simulation only: synthetic data, revision checks and per-entity idempotency live in memory. No network requests are sent. Reloading or resetting discards all data and recovery requirements.

Choose a scenario

Concurrent update

Edit a draft, then simulate a remote update. Accept remote values, rebase local edits or merge individual fields.

Unknown update

Save once. The server commits but holds its response. Cancel waiting, then reconcile before editing again.

Unknown create

Create once with a held response. Recover the generated identity by logical mutation ID without creating a duplicate.

Partial batch with uncertainty

Ada succeeds, Grace is refused and Katherine commits with an unknown result. Reconcile before starting a new write for Grace.

Selective retry with known results

Ada and Katherine succeed. Retry only Grace in the same session, preserving its logical mutation ID.

Recovery controls

Choose a scenario to begin. Starting a scenario resets the previous run.

Ready.

Authoritative server data

Reflected host data

Session snapshot

The retained snapshot preserves an uncertain draft, including per-entity batch results.