File deleted by another device: 2 options

The other kind of sync conflict: one device deleted a file while another is still editing it. Again, Slima doesn't decide for you.

What triggers it

1. On the desktop, you open Chapter 8 of The Lighthouse Keeper and write a passage
2. On mobile, tidying the bookshelf, you move Chapter 8 to trash
3. The desktop syncs and finds "this file was deleted elsewhere" — but you still have unsynced edits on the desktop

The same conflict dialog opens, this time headed Deleted on another device. There is no other version left to compare against, so instead of a side-by-side diff you get the copy still sitting on this device next to a short note explaining that the file is gone on the server.

Two options

Keep Mine

Don't accept the deletion — keep the file:

• Your edits stay, and the file isn't deleted
• The file is queued to go back up, so the other device gets it again on its next sync

Accept deletion

Take the other device's deletion at face value:

• Slima asks you to confirm first, and tells you plainly that the copy on this device will be removed too
• If you want it back afterwards, pull that one file out of the book's version history — see Restore a version

There is also Resolve Later, which closes the dialog without deciding; the conflict comes back next time. "Keep Both" is not offered in this case — there is no second version left to save a copy of.

Both ways are recoverable

If you pick wrong:

• Chose "Accept deletion" then reconsidered → restore that file from version history
• Chose "Keep Mine" then decided you did want it gone → use the normal delete flow

Either way, no permanent content loss — version history and the trash give you two ways back.

Restoring is not just the text coming back, either: pull a chapter out of version history and its notes, the draft you hadn't saved yet, and the tabs you had it open in come back attached to it. As far as everything pointing at that chapter is concerned, the restored one is the same file — nothing quietly loses its links.

Why Slima doesn't auto-decide

An auto-rule like "last action wins" sounds reasonable, but it backfires:

You wrote for a solid hour on the desktop; mobile accidentally deletes Chapter 8 — if "last action wins," that hour of writing is gone.

So for delete conflicts, Slima always makes you choose — it never decides on its own.

Related

• Content-conflict resolution
• Sync status
• Restore from trash