Cloud Sync WebDAV auto-sync fails on game close (Windows) but manual sync succeeds

Is there an existing issue for this?

• This is a bug in RetroArch frontend
• I have searched the existing issues

Description

On Windows, RetroArch Cloud Sync using a WebDAV backend consistently reports “Failed to sync” right after closing content, but performing a manual sync immediately after always succeeds.

---

Additional context

This looks like a timing/flush or Windows-specific auto-sync issue: the auto-sync path triggered on content close may be firing before save/state files are fully written or unlocked, causing a failure toast even though a later manual sync succeeds without changes to config.

---

Potential fix

Maybe adding a delay of 1 or 2 seconds after content close would give the core enough time to release the save file for a successful auto-sync?

Expected behavior

After closing content, Cloud Sync should complete successfully and match the behavior of manual sync.

Steps to reproduce the bug

1. Install RetroArch on Windows.
2. Configure Cloud Sync with a working WebDAV server.
3. Launch any core/content and play until a save/state is created or updated.
4. Close content / exit the game back to the menu.
5. Observe the Cloud Sync status toast/message.
6. Go to Main Menu → Cloud Sync → Sync Now (manual sync).

Version/Commit

1.22.2

Bisect Results

No response

Present in the nightly version

Yes, this is reproduced in the nightly build

Platform & operating system

Windows 11 25H2

Affected Cores

No response

Environment information

No response

Relevant log output

Start at the Cloud Sync auto-sync path triggered when content closes and compare it with Main Menu → Cloud Sync → Sync Now on Windows. Reproduce with a WebDAV backend and inspect timing around save/state file writes and locks; done means auto-sync succeeds after closing content and matches manual sync.