Why does Synology Drive keep creating conflict copies of my documents?

QUICK ANSWER

A conflict copy preserves competing edits or names that cannot be represented consistently on the client. Keep both copies until you compare their contents; deleting every file containing conflict can discard someone’s work.

Applies to: Synology Drive Client and Drive Server; two-way file sync.

Work through these checks

  1. Pause editing the affected document on all devices. Save separate copies of the original and conflict file outside the sync folder, then compare contents and modification details with the people involved.
  2. Read the suffix and client log. CaseConflict, WhiteSpaceConflict and similar naming errors need a corrected, unique filename. A timestamp alone does not establish which copy contains the wanted changes.
  3. Check whether the same folder is also managed by OneDrive, Dropbox or another sync tool. Use separate roots. Avoid simultaneously editing one document through an SMB share and an independently syncing local copy.
  4. Allow initial indexing to finish. Agree one editing method, use supported file locking or an appropriate collaborative editor, then put the agreed final document back. Test with a harmless document before resuming a busy shared folder.

Confirm the result

Both computers should receive the agreed contents without generating another conflict copy during the same controlled edit and sync sequence.

Before going further: Do not choose an overwrite or deletion policy for the whole team to fix one document. Keep independent backups before reorganising synced folders.

If you need help

Include these details in your ticket: Drive Client/Server and DSM versions, conflict suffix, task direction and a redacted log excerpt.

Updated 261107

Please Wait!

Please wait... it will take a second!