Note save, sync, and conflict states

Atlas saves note changes as you work and protects a newer saved version from being overwritten by stale editor state. Watch the visible save state before closing a tab or resolving a conflict.

What this page covers

Explain saving, local drafts, synchronization, conflict detection, reload or recovery actions, and data-loss stop conditions.

Note save states

A local draft can appear before its first server save completes. A saving state means changes are still being persisted. A saved state means the current editor version was accepted. An error means you must keep the tab open and retry or copy the unsaved text.

Resolve a conflict

A conflict means the saved note changed after the editor loaded it. Stop editing. Read the conflict message, preserve any unsaved text, and use the offered reload or recovery action. Do not repeatedly save over a conflict.

If recovery fails, copy the current text to a safe temporary location and contact support with the project name, note name, approximate time, and visible error. Do not send sensitive source content unless support requests a secure path.