Saves, versions, and checkpoints
Understand dirty state, autosave, conflicts, history, and non-destructive restore.
Saving, version history, and checkpoints protect different parts of your work.
Save states
- Dirty means the graph has local changes.
- Saving means storage is in progress.
- Saved means the latest accepted changes are stored.
- Offline, error, or conflict require recovery before you assume the latest edit is stored.
Autosave runs while you edit, and manual Save is available whenever saving is allowed.
Versions and recovery entries
History can include the current version, recovery entries, named checkpoints, and technical entries. Use filters and pagination to find older items.
Previewing an older version opens it in read-only mode. It does not replace the editable graph.
Restore is non-destructive
Restoring creates a new current version from the selected historical content. The selected version remains in history. Save any current changes before starting a restore and verify the resulting graph afterward.
Checkpoint retention can depend on your plan. The checkpoint dialog shows the effect before creation.
Related documentation
- Save and resolve conflictsProtect local edits, recover from offline or error states, and choose the correct version after a conflict.
- Create checkpoints and restore versionsCreate a named recovery point, preview history safely, and restore without deleting older versions.
- Troubleshoot save, offline, and conflictsProtect local edits and recover when the editor cannot confirm the latest saved version.