Synchronize. Backup. Bootable Backup.

Whatever your backup or sync scenario, ChronoSync Express has got you covered!

Back to more tech notes


TNCSX-0004 - Handling Conflict Errors in ChronoSync Express

September 12, 2014


Conflicts arise in bi-directional syncs only. It is simply a file or folder that has changed on both sides of the sync since the last synchronization. This change may be one of the dates, file size, or another file attribute.

Since both files have changed, ChronoSync Express wants to make sure the correct file is copied so an error is created. If a scheduled synchronization is run an error is posted to the sync document Log. If you run the synchronization manually, an error message will be presented during the sync and you can then choose the file you want to use. If you are not sure of what file to use, "Skip" the conflict and investigate both files. Once you determine the correct file to use, re-run the sync and choose that file when the conflict sheet is presented to you.

You can handle Conflicts automatically by going to the Options Panel under the 'Reporting and Error Handling' section. Click the popup menu next to 'Conflicts:' and select what you want ChronoSync Express to do when it encounters a Conflict.


'Attribute Conflicts' occur when a date or other file attribute appears to be out of sync. It doesn't affect the data in the file and is a quick item for ChronoSync Express to re-sync. The recommended setting of the 'Conflict:' popup menu is 'User Newer'.

To troubleshoot this issue, you might want to verify that the two targets in your sync document are syncing to the same time server automatically. The two computers being synchronized might have clock settings that are out of sync. You should check and configure the clock settings in System Preferences - Date & Time. Be sure to configure them both to connect to a network time server.

Also, some applications play havoc with dates. We have seen MS Office applications update creation and modification dates unexpectedly. So maybe an application you are using is triggering the date change. Try to pay attention to the files that generate a conflict and then try to figure out what you used to last modify or view the file.


Many times, accessing a folder, or spotlight indexing, can result in a change to its modification date. This triggers the conflict. The recommended setting of the 'Conflict:' popup menu is 'Use Newer'.

Since a large number of Folder Conflicts can make it easy to miss conflicts on legitimate files, you can use the technique explained below to synchronize and resolve all folder conflicts before syncing the actual files.

  1. Set up a second sync document for the same two targets.
  2. In the new sync document, create a Simple rule to skip all files. Something like "File size is less than zero" should eliminate all files.
  3. Make sure deletions aren't synchronized, just to be safe.
  4. On the Options Panel, in the 'Reporting & Error Handling' section, set the 'Conflicts:' popup menu to "Use Newer".
  5. Run the new sync document first, then run your regular sync document afterwards.
  6. Add them both to a container, if you want to run/schedule them as a single entity.


Sep-12-2014 - Created from Internal Support Notes.