Understand autosave and recover from a save conflict
Protect your draft when saving is interrupted or another session changes the project.
Wait for the save result
The editor works with a draft. Confirm that the application's save state has settled before closing the tab, creating a revision, or assuming another device has the latest changes. Seeing a change on the canvas is not the same as receiving confirmation that it was saved.
When saving is interrupted
- Keep the current tab open and record the visible message.
- Check whether your connection or sign-in session was interrupted.
- Follow the recovery or retry action offered by the editor.
- Confirm the recovered design and save state before continuing.
Local recovery data can help preserve an editing session, but it is not a server backup. Clearing browser storage or switching devices may remove the context needed for recovery. Avoid those actions while an unsaved draft is still open.
When another session changed the project
A conflict protects a newer version from being overwritten by an older draft. Review the current server state and the recovery choices shown. Do not repeatedly resubmit an old change without checking what another editor saved.
Get help without losing context
Include the project, time, save message, browser, and whether another tab or teammate was editing. Describe the last successful change and the change still pending. Support does not need your session cookies. Once the draft is stable, create a saved revision for a traceable handoff.
Include this guide and what you tried in your ticket so we can pick up from there.
Contact support