My Changes Are Missing

What to check when work seems to have vanished, and how to recover it with autosave and undo.

Applies To

Every liveworkspace app

Work in every app 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 file, 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

  1. 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.
  2. Check the right file. It is easy to have two similar files open. Open your files and confirm you are in the one you edited.
  3. 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 files. If you just signed in, your guest files 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.
  4. Reload the page. A refresh reloads your saved file and clears any temporary display issue.

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. Keep this tab open to save when you reconnect.) Autosave keeps trying, so reconnect and leave the tab open until your changes go through. Other messages mean retrying will not help on its own:

  • Your sign-in has lapsed: sign in again to keep the changes.
  • You can no longer edit this: 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 save that did not reach the server shows a message at the bottom of the screen; autosave keeps retrying.

"A new version of every app is ready". When every app is updated while you have a file open, and the update changes how files 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. If the update is still on its way to you, it says so too: try again in a minute. The notice appears like any other notice and stays until you close it or press Reload. Closing it (×) hides it until a newer update arrives; 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.

Undo steps back your most recent change; redo puts it back.
  1. Press Undo (Cmd/Ctrl+Z, or the undo button at the bottom-right) to step back your most recent changes, one at a time.
  2. Press Redo (Cmd/Ctrl+Shift+Z, or Ctrl+Y) if you went back too far.
  3. 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 file is not gone either: it waits in the Trash for 30 days until you restore it. A file left empty for 30 days moves there on its own, so look there too.

If an AI tool or a script changed the file, 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 things on the same tab is safe. Edits travel as changes to individual elements and merge one by one, so your move of one item 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 thing is the case to know about. There the last edit to arrive wins. In practice the editor heads this off by showing something as locked while another editor has it selected (every element of a multi-selection, and for a moment after they let go, until their change is saved), 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 file, still without a page reload.

If you have checked the right tab, file, and identity, reloaded, and the change is still missing, contact us with the file URL and roughly when you made the edit.

Was this article helpful?

Still need help?

Try Troubleshooting, or tell us what you were trying to do.

Contact us