We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
The Badge shows a file was edited 420 years ago
Is anyone else having issues with Badge, randomly showing "<user> last edited this file 420 years ago".
it seems to affect both mac and windows users and appears to be random- in that we can't ...
I know this issue sucks big time, and I hate being the bearer of bad news...but
https://help.dropbox.com/installs/badge-overview
The timing and exact functionality of these features may change, and Dropbox doesn't provide warranties on the performance of these features.
We have been trying to get you guys to resolve this issue for well over a year now.
This is the response I got from your team today.
The team has advised me that a resolution for this issue may come at a later date, however, the team doesn't have an exact ETA at this stage.
If you have any questions, please let me know.
This is affecting our ability to run our business with effective data and communication between our team members.
Completely unacceptable.
Thank You, TeeDub!!!
We have the same issue and here's what I think of DropBox's reply to you:
That is COMPLETE AND TOTAL BS!!
and yes, I meant to yell at you;-)
In our shop we are running 3 dif versions of Windows & 3 of macOS.
Dropbox App fully updated on all machines and we still get "edited 421 years ago" on some files.
it's the same wrong edit date on a few files across ALL users and all computers.
One of the main reasons we use dropbox is because of the file version mgmt and the badge showing who and when a user edited a file.
That functionality is critical to our business ........all day long, every day.
If y'all cannot resolve this (clearly dropbox) error then I will have to seek another vendor's solution.
Which, I don't want to do as I like dropbox ............except for this unresolved bug.
Dropbox has ignored this issue for more than a year, has offered useless advice and refused to investigate the issue properly.
We still have the issue, and the syncing issue might be part of the cause- but how about Dropbox actually checks and provides a fix.
It isn't just excel files either. I can't see how the sync issue is responsible as when you open a file on your desktop- it downloads a copy so must therefore be synced with the server.
There's a lot I like about dropbox but if the 420 years bug remains unfixable you wonder if they have really tried.
hey @dropboxsupport any chance of some interest in this issue???
If anyone is curious about 1601, it's because computers store the file modification time as the number of intervals that have elapsed since the "epoch", aka Time Zero, and on Windows, the epoch is January 1st 1601 (Why is the Win32 epoch January 1, 1601? - The Old New Thing (microsoft.com))
Hence if the stored file time defaults to zero, it'll come out as 1/1/1601, i.e. 421 years ago.
We see this pretty often at work but it's more a cause of mirth than inconvenience, it always sorts itself out after a short while.
