Child Item

accidentally overwrite the newest version of my file (syncing on more than one device)

KamahI

I accidentally overwrite the newest version of my file:

Saved on device 1

Synced

Started Device 2

Didnt Sync, wondered why i didnt see the new Version, saved the current file overwriting what was saved local

started Syn

realized that my file was overwritten now with what was saved on device 2..

File History and dropbox.com/events both doesnt seem to help me....

also found this: https://help.dropbox.com/en-en/delete-restore/missing-or-corrupted-file-support#event but it seems I cant send an email anymore

Any ideas?

Find more posts tagged with

Restore

File Access

FAQ

LOL

New

Accepted answers

KamahI

Hi Jay! First of all, yes I am absolutely sure to be logged into the same account on both devices, since I only have one account.

Thing is, the events page says, I actually changed the file I am looking for 5 hours ago, what only possible can be happened on device 1 though when I download the provided file from there: [Removed as per Community Guidelines]

It gives me the file version I uploaded with device 2 just an our ago or so (and overwrote the newer file version...)

All comments

Jay

Hi @KamahI, thanks for bringing this to our attention.

Regarding support options, they vary depending upon your current plan. You can view all your available options when signed into your account on this page.

If the events page isn't showing the changes made by device 1, nor the version history of that file from that device, then this means that the file didn't sync to the site originally.

Are you certain you're logged into the same account on both devices?

This will help me to assist further!

KamahI

Hi Jay! First of all, yes I am absolutely sure to be logged into the same account on both devices, since I only have one account.

It gives me the file version I uploaded with device 2 just an our ago or so (and overwrote the newer file version...)

Jay

If there isn't any version history for the file, then it means that it didn't sync the changes somehow. Without the history, it wouldn't be possible to recover the data, even from our end.