In SecuriSync, you may encounter conflicted file / folder copies.
Unlocked file can be edited by several users at the same time. The user who first starts editing is called Master editor. They can save changes changes to the original file. Updates made by other co-editors will be saved as separate conflicted files in the same folder in SecuriSync. The same will happen if user made some changes in a shared file on the desktop, while the desktop client was offline.
Such files can be merged with the original file only manually.
Conflicted files have the following naming convention:
Filename (Conflicted copy YYYY-MM-DD for Username)
Our Shared File (Conflicted copy 2015-10-01 for
To avoid conflicts, use the Lock functionality. While the file is locked by one user, others will be able to access the file only with View permissions.
Sometimes you may find folders with a numbering postfix in the folder name, e.g. 'New Folder (2)'.
To resolve the issue let the user delete the folder from the web client or delete it in the Admin File Management.
|Reason||How to resolve|
If the user accepted sharing invitation having another folder with the same name in the My SecuriSync directory.
|Such folder may not be displayed on the desktop or mobile client, if it is stored on the cloud in a trashed state. The user can check such folders on the web client.||
To resolve the issue:
|If the user created a new folder while having the folder with the same name in the same directory.||
|Sometimes folder appears again with the (2) in the name after user tried to delete it.||This happens because on the server folder contains the file that is excluded from the synchronization. Such file was excluded from synchronization after it had been uploaded to the server.||Delete folder from web client or from Admin File Management|
|If the index.db file was re-created.||It may happen because of the application crash or if support asks to delete some files used by the SecuriSync application for another issue troubleshooting.||