We just had a rather unpleasant surprise with the message above (more specifically, with the functionality behind that).

In a cloud project comprising more than 50 individual files, we had to make subsequent changes. At one point, we encountered the message shown above; after accepting the overwrite, we found out to our, er, surprise that the local versions had in fact been the most recent ones. But these are now gone.

While it might probably be impossible to completely avoid such situations, the information provided in this message should be more detailed, including:

- the date and time when the local version was last saved;
- the date and time when the cloud version was last saved;
- perhaps even the file sizes.

This would allow to take a more informed decision regarding overwriting.

Follow-up questions:

- Are there any workflow steps that would prevent the mismatch in the first place?
- Would it be feasible to save backup copies before overwriting?

MTIA, Ralf