How-to guides
Recover after a missed collaboration update
Complete a task or diagnose a specific problem.
1. Treat the saved revision as the ordering signal. A preview is not a durable revision and should not be used to reconstruct saved state.
2. On a gap, reconnect, or rate-limit recovery, follow the snapshot/resynchronization contract in the realtime protocol. Replace stale assumptions with authoritative state rather than replaying arbitrary transient previews.
3. Verify the canvas state and undo/redo availability after synchronization. Redis fanout delivers events; PostgreSQL supplies the recovery truth.