Deleted Files or a Sync Conflict? How to Tell the Difference
Desktop clients create ‘lost file’ tickets that are really caches, conflict copies, selective sync, or path-length failures. A diagnostic path before you declare data loss.
- Look at the web app first. If the file is there, you do not have a cloud delete.
- Conflict copies, ‘computerName’ duplicates, and Files On-Demand placeholders all look like loss to users.
- Path length, invalid characters, and offline mode explain a surprising share of tickets.
- Fix the client, then reconcile copies — do not restore from backup over a healthy cloud object.
The ticket that is not a restore
Helpdesks spend hours “recovering” files that were never deleted in the tenant. The user looks at Explorer or Finder, sees an empty folder, and assumes the worst. The web app still has yesterday’s work. That is a sync problem, and treating it as a mass delete can overwrite good cloud data with an empty local tree.
Diagnostic order (ten minutes)
- Open the same path in the browser (OneDrive / SharePoint / Drive). Present in the cloud? Then local client, not recycle.
- Search by file name across the tenant. Users misremember folders; Shared Drives and SharePoint sites hide items in plain sight.
- Look for conflict artifacts: names like File (computer’s conflicted copy), -Desktop suffixes, or duplicates with timestamps.
- Check selective sync / Choose folders / Files On-Demand. A cloud-only placeholder that failed to hydrate looks like a 0-byte or missing file.
- Check path length and characters. Windows MAX_PATH and
*?|in names still break clients that the web UI accepts.
What each symptom usually means
| Symptom | Working theory | Do not |
|---|---|---|
| Empty folder locally, files on the web | Filter, pause, or failed hydrate | Restore backup over the library |
| Two similar files, one older | Conflict copy | Delete the ‘extra’ one until you compare |
| Office file says locked / upload blocked | Client merge failure | Force-save from the stale laptop as the winner |
| Gone on the web and locally | Actual delete | Waste time reinstalling the client first |
Reconcile conflict copies like an adult
Open both. Check modified dates and content — dates lie when a laptop clock is wrong. Keep both until a human picks a winner, then rename the loser instead of deleting it for a week. Many “lost paragraphs” were in the conflict copy the user ignored.
When it really is a delete
Web and local both empty, activity log shows delete, Trash has the items — switch to the mass-delete playbook. If the web still has the file, stay in sync-repair: pause, free disk space, shorten paths, resume, then hydrate a test file.
Related reading
True overwrites belong in version history. True deletes belong in the first 60 minutes.
