OD4B sync seems to screw up modified information

Copper Contributor

Dear community,

We have some random files in SPO, which are set to a modified date of 1/1/1980:


I don't have any evidence that sync client is the root cause, but I've found some hints that incomplete transfer of data will let files with this modified value set. Seems that robocopy has the same behavior when a transfer is incomplete, maybe MS is using the same technology :)


Has anyone experienced that issue too?

Thx in advance for any feedback.....


1 Reply

@Nicolas69 yes we have this issue too. I'm not finding many hits or solutions with this one. Did it go away for you?
We have tightly controlled documents and customers not happy with this.