If the target path is on a FAT/FAT32 partition, files over 4GB won't sync due to FAT/FAT32's file size limit. Try a different path or contact support if not. If it's not FAT/FAT32, check the product log or contact support with the log folder.
The issue may be due to the Windows system's maximum path character limit being exceeded when syncing files or folders to a target path, preventing access to them. However, the files themselves are not damaged. To resolve this, you can try cutting the parent directory of the affected files or folders to a new path with fewer characters, and if the issue persists, contact technical support with the log folder.
The SYSTEM user may not have permission to access the source files, which prevents File Sync from working. To resolve this, add the SYSTEM user's permission to the security attribute of the file and try File Sync again. If the issue persists, contact technical support and provide the log folder.
File Sync does not currently display sync progress through an executing interface or tray notification. Progress can only be viewed when creating a new task, and later it is not visible. To track the progress, users must check the status of files in the target path or the log.
File Sync only supports one-way monitoring and syncing, meaning it tracks changes in the source files and copies them to the target path, but doesn't monitor the target path for changes, so it won't sync when changes occur there.
🔔 Note: File Sync tasks only support one-way sync, such as syncing from A to B. Creating a task from A to B and then another from B to A can cause a circulating sync, leading to increased CPU usage, slow system performance, and potentially corrupted source files.
File Sync monitors all subfolders and files, including temporary files, in the source folder, which means temporary files will also be synced during the process. To ensure data safety, the program offers a "target files will be deleted when deleting the source files" function in the File Sync setting.