Misleading timestamp in File Sync Errors

If I open File Sync Errors, I see multiple errors with completely wrong timestamps like

Pictures                          Server error                                                                        Just now
Downloads  some.pdf    Concurrent updates to file. File is saved as conflict file       8 hours ago

The issue exists in Windows 7.0.7 and Linux 7.0.4 clients.

There are no fresh errors in the logs. But the timestamps are always the same, no matter when File Sync Errors is open.

While we are talking about it, it would be nice to see the actual time of the errors, not “Just now” or "8 hours ago.

1 Like