Offline editing and conflicts
The editor uses IndexedDB as a local cache for drafts. It synchronizes draft changes with the server while the connection is available.
If the server is unavailable
Section titled “If the server is unavailable”An App that has a usable cached configuration and SVG can open from that cache. You can continue editing its draft. Watch the offline/synchronization state and keep the same browser profile while working.
A never-opened App, an uncached SVG, new database results, and external Google services are not guaranteed to be available offline. Offline App editing does not turn Database into a fully offline database editor.
When the server becomes reachable, the editor attempts to synchronize. If the server revision has changed, it must resolve that conflict instead of blindly overwriting either side.
If a draft is missing on the server
Section titled “If a draft is missing on the server”A missing remote draft is not automatic permission to discard its local cache. The editor can offer recovery from retained local work. Inspect the recovery choice and preserve the draft you need.
A draft explicitly deleted with confirmation is different from a server that failed to return it during an outage.
If another tab or editor changed the draft
Section titled “If another tab or editor changed the draft”Do not keep publishing from an outdated buffer. Review the conflict state. Pull changes, when offered, replaces the editor’s current content with the server’s version after confirmation. Use Branch in new draft or otherwise preserve your desired local work before accepting replacement.
A successful network request alone is not proof that the desired local configuration became the server’s current revision. Wait for acknowledged synchronization and verify the intended draft before publishing.
Storage limits and backups
Section titled “Storage limits and backups”Browser storage can be cleared by private browsing, browser cleanup, profile changes, or storage pressure. The cache is a recovery aid, not your only backup.
Do not clear site data to fix a startup or sync problem while it contains your only copy of unsynchronized changes. Keep server/database backups and uploaded SVG backups independently of App versions.