What is "Invalid Modification Time" error?

[harryPotter]

I have seen this error appear twice on two different files and I suspect that this may be what has been causing my sync to not work properly?  They are small files <100KB.

[GreatMarko]

Check the system clocks on your devices and the modification time on the files themselves. Sync has determine that these files have invalid modification times (i.e. they appear to have been modified in the future - which isn't possible).

Correcting your device's system clocks (if that's the case) should resolve the issue, otherwise, you'll need to "touch" (modify) the files in question on a device with a correct system clock so that the files then have a "valid" modification time, and can sync.

[harryPotter]

 

On 2/27/2017 at 1:08 PM, GreatMarko said:

Check the system clocks on your devices and the modification time on the files themselves. Sync has determine that these files have invalid modification times (i.e. they appear to have been modified in the future - which isn't possible).

Correcting your device's system clocks (if that's the case) should resolve the issue, otherwise, you'll need to "touch" (modify) the files in question on a device with a correct system clock so that the files then have a "valid" modification time, and can sync.

This happens quite often on my computer, about 50% of the time.  My system's clock is synced and correct.  Resilio is the only app that reports this type of error?

This happens when I move files into a synced folder.

How do we reduce the amount of occurrences of this type of error?

Sync v:  2.5.9 (1088)

 

[harryPotter]

Help, anyone?

[Helen]

if you go and check the file's time in its properties, what is it? 

[harryPotter]

On 11/9/2017 at 3:18 AM, Helen said:

if you go and check the file's time in its properties, what is it? 

The time is in the future.  But it only changes after I move files into a Resilio synced folder?  If I move files into a normal WIndows folder, the modification time doesn't change into the future.  This happens about 90% of the time.  What's going on?

[Helen]

I'm not sure that simply moving the file to sync directory will change its timestamp.  Unless, there's the same file with wrong timestamp on remote peers? What does Sync History say about this file? 

[harryPotter]

On 11/10/2017 at 11:58 PM, Helen said:

I'm not sure that simply moving the file to sync directory will change its timestamp.  Unless, there's the same file with wrong timestamp on remote peers? What does Sync History say about this file? 

1.  Remote peers do not have this file.  It's a new file that I move into a Sync folder.

2.  How do I look at the Sync History?

 

Thank you!

[Helen]

move the mouse cursor over to "history' icon in Sync UI and do a left-click on it..... 

 

[harryPotter]

Thanks, this is what it says...

 

 

 

[Helen]

so please check the timestamp on these files. 

[harryPotter]

The time stamps are correct BEFORE I drag and drop them (from root folder of same drive) into the Sync folder (of the same drive).  But, after I drop them into the Sync folder, the modification time stamp changes to a future time stamp, which is why it has an error warning.

If I drag and drop the same file into a normal Windows 10 folder, there is not modification error.  The error only occurs when dragging and dropping into a Sync folder.

[Helen]

'm not sure that simply moving the file to sync directory will change its timestamp.  Please send debug logs from all peers to support and mention file names, and give details about these files - what they are, where' they 're moved from and to, how they're originated on PC. https://help.getsync.com/hc/en-us/articles/206664730-Collecting-debug-logs-

 

[felipe]

Hi all! Has this ever been resolved? I have a friend that's encountering the same issue.

He moves a file into a synced folder and it gives the warning about invalid modification time.

[AlexC]

On 11/27/2019 at 11:31 AM, felipe said:

Hi all! Has this ever been resolved? I have a friend that's encountering the same issue.

He moves a file into a synced folder and it gives the warning about invalid modification time.

@felipeyes. it's necessary to check file modification time of files mentioned in history as invalid and correct it.