The content on this page provides answers to frequently asked questions about syncing with Desktop Connector. It covers topics such as sync frequency, common syncing issues, and troubleshooting steps for files and folders stuck in a Sync Pending state or not syncing.
Having opened or edited the contents of a project within the last 24 hours, Desktop Connector checks every 30 seconds for any changes made in the cloud (Docs only) and syncs these changes back to your Desktop Connector workspace.
There are three categories of sync issues:
Failed syncs will display an error message in the Home Screen citing a failed upload.
They will also generate an error in the home screen and display a red error icon in File Explorer .
There are many reasons syncs may fail. Some of those reasons for this type of issue could be:
This issue is characterized by a perpetual blue Sync Pending status in File Explorer but no upload operation reflected in the Home Screen. Some reasons for this type of issue could be:
This type of issue is when changes or updates in the cloud fail to appear in Desktop Connector, though the Desktop Connector home screen displays “Up to Date.” This can be caused by:
Try these methods before adding/removing projects, using the Reset Utility, or uninstalling the product to reduce the likelihood of losing unsynced changes and reselect projects. You can check the UnSyncFileData.txt
or the UnSyncFolderData.txt
to find out if you have files that did not sync before doing this step.
Files or folders that are not uploading to the cloud and remain stuck in a "Sync Pending" state (that is, a blue sync icon is stuck as the status), you might find this video helpful to determine whether any of the suggested workarounds can resolve your issue. This video provides a detailed example of workflows where you may encounter files or folders in a sync pending state.
Methods of resolving folders which are not syncing (make sure that Desktop Connector is running at the time):
Add a new file to the folder and see if it syncs.
COPY the folder to a local disk location (as a backup of the data), then COPY the folder back to update the folder and kick the system to sync the folder.
Unselect /Reselect the impacted project from the Project Selection dialog. This is a last resort. This method will lose cache and unsync'd changes from the entire project.
Reset Desktop Connector: This is a last resort. This method will lose cache and unsynced changes from every selected project. These steps should be taken to identify unsynced data so they are not lost.
Use Copy as opposed to Move . A Move would act as a Delete from the original location once the folder is successfully moved. We do not want to Delete since that would lose version history of the files in the folder, so we want to perform a Copy in this scenario.
Often files that are not syncing are caused by activity in the workspace while Desktop Connector is not running. When files have the pending sync icon status and do not sync, that may be an indication of a corrupted file. These files should be identified in the Diagnostics Logs explained in Online Help topic Collecting and Viewing Sync Data.
Methods of resolving files which are not syncing (make sure that Desktop Connector is running at the time):
Add a new file to the folder and see if it syncs.
Go to section Folders that are not syncing because the issue is likely the folder is bad.
Open one of the unsynced files, make a small edit, save the file: Often this is enough to cause a problem file to sync.
Copy one or more unsynced files to a local disk location and then copy the files back into DC to create an updated version: Often this is enough to cause a problem file to sync.
Make local copy of all files reported in the UnSyncFileData.txt as a backup so you do not lose unsynced edits.
Unselect /Reselect the impacted project from the Project Selection dialog. This is a last resort. This method will lose cache and unsynced changes from the entire project. Once the project is resubscribed, copy the files back into the project. These steps should be taken to identify unsynced data so they are not lost.
Reset Desktop Connector: This is a last resort. This method will lose cache and unsynced changes from every selected project. These steps should be taken to identify unsynced data so they are not lost
Use Copy as opposed to Move . A Move would act as a Delete from the original location once the folder is successfully moved. We do not want to Delete since that would lose version history of the files in the folder, so we want to perform a Copy in this scenario.
Related Concepts: