Work in livediagram is saved automatically as you go, so missing changes are usually hiding rather than gone: you may be looking at a different tab, a different document, or a different identity than the one you edited under. This checklist walks through finding them and, where needed, recovering them with undo or the Trash.
First, find them
- Check the right tab. Each tab stores its own content. If a tab looks empty, confirm you are on the tab you actually edited. See tabs.
- Check the right document. It is easy to have two similar documents open. Open your documents and confirm you are in the one you edited.
- Check the right identity. Guest work is tied to the browser that made it. If you switched browsers or devices, you are looking at a different guest identity's documents. If you just signed in, your guest documents move into your account; if they have not appeared, reload, and if they still do not show, contact us with the report from Copy Diagnostics. See working as a guest.
- Reload the page. A refresh reloads your saved document and clears any temporary display issue.
- Check the tabs beside a Plan tab. If a Plan tab's boards and sheets seem to have gone, or it split into several tabs, an older Plan tab was updated to the new layout: each board and sheet moved to a tab of its own, right after it, and the tab became a Dashboard showing them. Your cards are untouched. See Plan Mode: Good to Know.
How saving works
Changes are saved automatically after you make them, per tab, to the server, not just to your browser. There is no manual "save" to forget. Because saving is per tab, editing one tab never disturbs another, and an empty, never-loaded tab is prevented from overwriting a tab that still has content.
There is no "saved" indicator to watch, because saving is the normal state. What you will see is a failure: if a save cannot reach the server, a message at the bottom of the screen says Couldn't save your changes. Check your connection. (If your browser is offline it says You're offline. Your changes will save when you reconnect. Keep this tab open.) Autosave keeps trying, so reconnect and leave the tab open until your changes go through. Two other messages mean retrying will not help on its own:
- Couldn't confirm you're signed in: your session has lapsed. Sign in again to keep the changes.
- You no longer have permission to edit this document: the share link was revoked or you were removed from the team, so autosave has stopped. Export a copy of the tab to keep your recent work.
"A new version of livediagram is ready"
When livediagram is updated while you have a document open, and the update changes how documents are stored, a small notice at the bottom of the screen asks you to reload. Nothing happens until you choose: Reload first waits until your latest changes are saved, then reloads, and if they cannot be saved yet it tells you so and stays put. Not now hides the notice; reload whenever suits you.
Recover a recent step
If you have just undone, moved or deleted something by mistake, Redo and Undo are your recovery tools.
- Press Undo (Cmd/Ctrl+Z, or the undo button at the bottom-right) to step back your most recent changes, one at a time.
- Press Redo (Cmd/Ctrl+Shift+Z, or Ctrl+Y) if you went back too far.
- Undo covers your own recent steps in this session. It is cleared when you reload, and it never reaches into someone else's edits.
A deleted document is not gone either: it waits in the Trash for 30 days until you restore it. A document left empty for 30 days moves there on its own, so look there too.
If an AI tool or a script changed the document, the note that appears with its change has an Undo that puts it back, separately from your own undo history.
What collaboration does and doesn't protect
Two people editing different elements on the same tab is safe. Edits travel as changes to individual elements and merge by element, so your move of one box cannot overwrite somebody's edit to another. That was not always true, and it is the single most common shape of "my change vanished".
Two people editing the same element is the case to know about. There the last edit to arrive wins. In practice the editor heads this off by showing an element as locked while another editor has it selected, so you can see that it is spoken for before you start.
If a connection drops, the editor catches up on reconnect rather than reloading: it asks for what it missed and applies it. Your viewport, your selection and your undo history survive, so a wobbly connection no longer costs you your place. If it has been away too long to catch up, it re-fetches the document, still without a page reload.
If you have checked the right tab, document, and identity, reloaded, and the change is still missing, contact us with the document URL and roughly when you made the edit.
Was this article helpful?