Crash recovery and reconnecting

A crash, a dropped connection, or a dead laptop doesn't cost you the session. Reload, and everything you and your collaborators made is still there.

The save-status indicator

A small status pill sits at the bottom-right of the canvas, reflecting exactly what's happening with your work in plain language:

- Unsaved changes: you've edited since the last save.

- Saving…: actively writing right now.

- Saved: everything is safely stored.

- Offline — will retry: the connection is currently down, but nothing is lost; Formo keeps trying and will catch up the moment connectivity returns.

- Saved locally: your work is safe on your own machine even though the server-side sync hasn't completed.

This is an honest indicator, not a decorative spinner: if something's wrong, it tells you plainly rather than staying silent.

What happens when you reload

On reload, Formo replays the full history of operations for that document, rebuilding exactly the state it was in — your own edits, and everyone else's, all reconstructed from the same op history everyone was streaming to each other during the live session. This isn't a periodic-snapshot restore that might be a few minutes stale; it's built from the same granular stream of individual edits that made the real-time collaboration work in the first place.

How Formo recovers your work

Lose connectivity while a session is live, and the status pill reflects it honestly rather than pretending everything's fine. Once the connection returns, you catch back up to whatever changed while you were offline. The same reload-and-replay mechanism handles both "I crashed and reopened the file" and "I was briefly disconnected and I'm back," because under the hood they're the same problem: reconstruct current state from the history, regardless of how you got disconnected from it.