Resolve unsaved drafts and version conflicts
Your goal
Preserve your edits while checking newer disk or client changes.
Before you start
Avoid refreshing, discarding the only draft or repeatedly resending stale writes. Copy critical drafts somewhere safe.
Steps
- Identify ordinary autosave versus a manual draft after accepting AI changes.
- Use Save draft or
Ctrl/⌘+Sfor manual drafts. - If disk content changed, reread both versions and merge explicitly.
- Design projects retain pending operations. Retry network errors; review version conflicts before reapplying.
- MCP conflicts require fresh revisions too. Annotation undo stops if another window changed the comments.
What to expect
After a confirmed save, switch, preview or quit with both originals and needed drafts accounted for.
If it does not work
Saving and index refresh are separate stages. A saved-but-index-pending result is not a reason to create duplicate content.
Next steps
- Review AI changes and save a draft
- Restore note history and recycled files
- Back up notes, comments and recovery data