Date integrity issues may arise whenever the source and destination locations of a Sync are on different systems, particularly when a remote server is used as a source or destination.

Due to the wide variety of remote server types supported, Files.com does not check data integrity when files are transferred during sync.

For some types of Remote Server, the sync will skip files that have changed since the start of the sync.

We rely on the next run of the sync to again check whether the file size and file name match on the source and destination of the sync. If a file is found to be a different size at that time, Files.com will attempt to re-sync the file.

Sync requires the source and destination systems to accurately report file sizes. When a remote server cannot do that, syncs will not work correctly. Any remote server that doesn't accurately report file sizes is incompatible for use with the Sync feature. Try using an alternative, such as an Automation or Remote Mount instead.