A game-save problem is safest to investigate before another session changes either copy. Stop playing on every device that uses the same account. Open a change log and record the platform, account identifier without its password, game title and build, device, local date and time with time zone, last confirmed progress, visible save slots, error text, and whether cloud synchronization is enabled. Photograph or capture the conflict screen. Do not choose a copy merely because one timestamp looks newer; connect each timestamp to the session that produced known progress.
Map the copies before acting
List every place a save may exist: the active device, another console or computer, removable storage if the platform supports it, and the cloud service. Steamworks documentation says matching files synchronize before and after sessions, files modified during a session upload after exit, users can disable cloud synchronization globally or per game, and a new computer downloads files before launch: https://partner.steamgames.com/doc/features/cloud?l=english. Those behaviors make account, device, session, and sync-state details essential parts of the record. The same documentation identifies `%Steam Install%\logs\cloud_log.txt` as a diagnostic log and notes that configured root paths can affect cross-platform save behavior.
Resolve a conflict from evidence
Steam Support explains that a conflict can appear when local and cloud files differ and both locations changed without a successful synchronization: https://help.steampowered.com/en/faqs/view/68d2-35ab-09a9-7678. Its conflict guidance tells users to compare dates and times with their actual play behavior before choosing. In the change log, write which session occurred last, whether it ended normally, whether the device was online, and which copy displays the expected character, location, inventory, or completion state. Preserve any copy that the platform allows you to back up before replacing another one. Never rename, move, or edit save files unless the game's own support instructions explicitly permit it.
Test one synchronization action
Choose one supported upload, download, or conflict-resolution action and record it before executing it. For PlayStation 5, Sony documents per-game synchronization status and manual upload or download controls for PlayStation Plus cloud storage: https://www.playstation.com/en-us/support/subscriptions/ps5-ps-plus-cloud-storage/. Record the displayed status before and after the action, the selected game, the direction of transfer, and the timestamps shown. Platform menus and subscription requirements differ, so follow the instructions for the exact account and system rather than translating button names from another service.
Launch the game only after the platform reports a completed operation. Verify the known checkpoint without creating substantial new progress, then exit normally and confirm the next synchronization. Close the log with the retained copy, the verification checkpoint, any file or platform reference, and any uncertainty. If neither copy can be tied to confirmed progress, pause and contact the game's or platform's support team instead of guessing. A careful unresolved record is better than a confident overwrite.
Sources
- Steam Cloud — Valve Steamworks
- Steam Cloud — Steam Support
- PlayStation Plus Cloud Storage for PS5 Consoles — PlayStation Support