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

A dialog appears:

"The Lighthouse Keeper / Chapter 8" was deleted on another device.

Your unsynced edits: (shows diff)

Choose:
[ Confirm delete ] [ Restore file ]

Two options

Confirm delete

Accept the other device's deletion:

• Your unsynced edits are kept as a version snapshot
• The file moves to trash

To recover later: Restore from trash.

Restore file

Bring the file back into the main folder:

• Your edits are preserved, the file isn't deleted
• The other device gets a "this file was restored" notification on its next sync

Both ways are recoverable

If you pick wrong:

• Chose "Confirm delete" then reconsidered → restore from trash
• Chose "Restore file" then decided to delete it → use the normal delete flow

Either way, no permanent content loss — version snapshots + trash, double protection.

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