OneDrive Cloud Sync in 25.04 keeps re-uploading unchanged files

Hello everyone,

I’m running TrueNAS SCALE 25.04 and using a Cloud Sync Task with OneDrive (Personal).
The sync works, but I’ve noticed that it keeps re-uploading files that are already present in OneDrive and have not changed.

It seems that the system treats these files as if they were updated, even though their content has not been modified. I’m wondering if this could be related to how timestamps or metadata are handled between TrueNAS and OneDrive.

My questions are:

  1. Is this a known behavior or bug with OneDrive integration in 25.04?
  2. Is there any built-in way to make Cloud Sync skip files that are truly unchanged?
  3. If not, what’s the recommended workaround that still uses the Cloud Sync Task feature rather than replacing it entirely with a custom script?

Environment details:

  • TrueNAS SCALE 25.04.2
  • Cloud Sync Task: PUSH, SYNC mode
  • Provider: OneDrive Personal
  • File Encryption Enabled
  • Files are mostly large media files, unchanged for months

Thanks in advance for any help or ideas!

1 Like

UPDATE: i found that the issue not happens if i disable the remote file encryption
In fact, reading the logs, the encrypted files are always replaced, not skipped

2025/08/12 13:42:07 INFO :TESTFILE.zip: Copied (replaced existing)

1 Like

I’m experiencing the same issue. In the past I’ve manually set up rclone with OneDrive and encryption on other machines (non ZFS-based though), and the unchanged files were not uploaded. Seems a bug of TrueNAS.

1 Like

I manually updated to the latest rclone version (1.71.0) and launched my cloud sync task. With this version I no longer saw all files getting re-uploaded.

Hi, how you manually updated rclone?

This is how I did it, basically installing the newer version in /usr/local/bin to override the built-in version. Note that I haven’t tested if this survives a reboot.

mount -o remount,rw /usr
rclone selfupdate --output /usr/local/bin/rclone
mount -o remount,ro /usr

1 Like

This issue still exists in the latest version when we enable the encryption. it is defenitely a bug. Updating rclone following the steps mentioned by @dowzer solved the issue tho. thanks.

I just created a PR to fix this issue in the source code: