The Cloud Sync Mistake
Tomas keeps his only copy of a 40-page dissertation in a cloud-synced folder. He edits it on his laptop at home, where the laptop is offline. Meanwhile, on his phone, he opens the same document and edits several paragraphs, then closes it while online. When the laptop reconnects, the sync client reports a conflict and offers two files: 'dissertation (Tomas's conflicted copy)' and 'dissertation'. He also has no local backup and the cloud service's recycle bin keeps deleted files for 30 days. He needs the version that contains both sets of edits, which neither file has.
1. Explain what caused the conflict and why neither file contains both sets of edits.
Read the worked answer
Cause: the same file was edited in two places while the devices were not in sync. The laptop was offline, so its changes were made to a local copy the service could not see. The phone edited the online copy. When the laptop reconnected, the service detected two divergent versions of one file and could not safely merge them, so it kept both and flagged a conflict.
Why neither file is complete: the service performed no content merge - it preserved each side rather than combining them. The 'conflicted copy' holds the laptop's offline edits; the other holds the phone's edits. Each is a branch, not a merge. The paragraphs Tomas wrote on the phone exist only in one file, and those from the laptop only in the other.
This is why editing the same synced file on two devices while one is offline is risky.
2. Recommend a recovery procedure to produce a single document with both sets of edits, and a change to prevent recurrence.
Read the worked answer
Recovery:
- Do not delete either file and do not let the client 'resolve' by overwriting - that would discard one set of edits.
- Open both files side by side (or open both in the same word processor) and manually merge: copy the phone-only paragraphs into the laptop version, or vice versa, checking each section.
- Save the merged result as a new file (e.g.
dissertation_merged_v1) so the originals remain as evidence until satisfied. - Verify the merged document against both sources before deleting anything; the 30-day recycle bin is a safety net but not a substitute for checking.
Prevention:
- Make a local backup copy in addition to the cloud copy - the single-copy risk is the real danger here.
- Avoid editing the same synced file on two devices; if working offline, sync before editing elsewhere.
- Where available, use the service's version history to compare and restore, rather than relying on conflict copies.