Rules
Part of Cloud storage basics: sync, sharing, backup, privacy, and recovery
Cloud storage problems: missing files, sync conflicts, and safe fixes
Cloud storage troubleshooting for missing files, sync delays, conflicts, full quotas, wrong accounts, online-only access, shared links, and deleted-item recovery.
What to take away
- Preserve local unsynchronized files before unlinking, resetting, or reinstalling a client.
- Confirm the account, folder, file state, quota, service status, and permissions.
- A missing file may be online, local, moved, deleted, filtered, or under another identity.
- Resolve conflicts by comparing content and dates, not by deleting one copy blindly.
- Recovery windows expire, so investigate deletion promptly.
Cloud problems are dangerous because a rushed fix can propagate loss. NCSC guidance on offline backups recommends keeping a backup copy digitally disconnected when not in use, because damage that reaches connected storage, including cloud storage locations, can reach every copy the account can touch. Pause and copy irreplaceable local files to a separate folder or offline medium before changing synchronization relationships.
File missing on one device
Check the service website under the intended account. Search by name and inspect recent, shared, trash, and version areas. Then check the device's sync status, selected folders, online-only state, and available storage.
If the file exists online, the device client is the likely layer. If it is absent online but present elsewhere, protect that remaining copy before reconnecting. Local, online-only, and cached files behave differently here, as cloud storage basics explains.
Synchronization is paused or stuck
Look for a paused, signed-out, full, frozen, locked, or processing status. Check system time, network, battery-saving restrictions, file names, path length, permissions, and whether another program holds the file.
Work from the client's own status indicator rather than guessing. A paused, signed-out, full, frozen, locked, or processing state each points to a different fix, and none of those states protects unsynchronized work until the state clears. Protect that work first, then clear the state.
Conflicting versions
Do not choose by modification date alone when clocks or offline devices may differ. Open both versions, compare content, save a clearly named preserved copy, then merge deliberately.
Record which device edited offline. Repeated conflicts may indicate two apps editing the same file format poorly or a shared folder with unclear ownership. Conflict copies are a property of synchronization itself, which file sync, backup, archive, and sharing compared separates from backup.
Storage quota is full
A full account can stop uploads and edits. Check trash, large files, device backups, photo libraries, shared-content accounting, and plan limits. Download or back up important content before bulk deletion.
Remember that removing a synchronized file can remove it across devices. Move it outside the sync root only after confirming that the new location is independent. Keeping one copy outside the synchronization path is an item in the cloud storage, sharing, and recovery checklist.
Online-only file will not open
Confirm internet access, account session, service status, permission, and free local space for download. Mark the file for offline use and wait for completion. A placeholder may display a name and size without holding the content locally.
If travel is near, test in airplane mode rather than trusting the availability icon.
Shared link fails
The owner may have moved the file, changed permissions, expired the link, closed the account, or restricted the recipient domain. Ask the owner to verify the exact object and your identity. Do not request a public link merely to bypass an access problem.
File was deleted
Stop further cleanup and check trash, recently deleted, version history, device backups, and another offline copy. Whether that offline copy exists at all is decided long before the deletion, in how to build a personal backup system. Record the deletion time and account. Do not permanently empty trash until recovery is complete.
Retention windows are real deadlines. Cornell IT's notes on trash in file collaboration services show trashed files being purged permanently after a set period, 30 days for its Box and Google Drive services and 90 for OneDrive for Business and SharePoint, and warn that purged items are gone. Windows differ by service and plan, so check yours before assuming a file can wait.
Duplicate folders after relinking
A client may create a new folder rather than merge an old one. Compare paths and synchronization status. Preserve both until file counts, checksums where suitable, and sample contents match. Never assume the folder with the newest creation date has the newest documents.
Escalation record
Give support the account type, platform, app version, exact icon or error, file path, last known good time, web status, local status, quota, and actions already taken. Do not post private links or recovery codes in public forums.
Common questions
Should I reinstall the sync app first?
No. First preserve local changes and identify the state. Reinstallation can alter sync relationships without solving account or quota problems.
Why does a file appear in search but not its folder?
Search indexes may be stale, or the result may point to a recent item, shared item, placeholder, trash, or another account. Inspect the full path.
Can I recover after emptying trash?
Possibly through provider support or another backup, but permanent deletion may be irreversible. Act quickly and avoid further changes.
Does changing the file name fix sync?
It can help when unsupported characters, reserved names, or path limits apply. Preserve the original and confirm the platform's current naming rules.
