When the system detects a mismatch between the local draft and the server copy, it opens a window with two options:
- Load version from memory — take the copy that is currently in the browser session.
- Load version from disk — take the copy that was previously saved locally (for example, in a past session).
Each option is labeled with a date and time — the moment when that copy was last updated.
Simple rule of choice
Pick the option with the more recent date — usually that's the last point you worked up to.
When to choose "from memory"
- You just opened the project and haven't edited in the current session — then "memory" equals a clean server copy. This is the safe choice.
- The current session was the "right" one, while the local draft on disk came from an accidentally opened other tab.
When to choose "from disk"
- Last time you closed the tab without "Save" and want to restore that work.
- The current session was short and without meaningful edits, while there is a more substantial revision on disk.
What happens to the version not chosen
The version not chosen will be replaced by the chosen one. That is:
- If you choose "from memory" — the server copy and the local draft will both be overwritten with the memory version.
- If you choose "from disk" — the server copy and the current session will be overwritten with the disk version.
After that, the window disappears and the project works as usual.
If you don't know what to choose
- Compare the dates — usually one is clearly more recent.
- If the dates are close and you don't remember what's in which version — choose "from disk" (this is safer: the disk usually holds your last full session). If as a result the project looks "wrong", contact your manager at the factory — the factory may have backup copies of the order.
Related topics
- Where this window comes from — what a version mismatch even means.
- Project versions — if you want to return to an even earlier server revision.
- Browser autosave — about the local draft and its limits.