Skip to content
English
Manage and Create Tickets
  • There are no suggestions because the search field is empty.

Folder stuck in sync pending state in FileCloud Desktop (Server 23.262.2 + FCD 23.253.4 / 23.253.5) - Fix Available

Status:  Fix Available – FCD version 23.253.6 

Affected versions: FileCloud Server 23.262.2; FileCloud Desktop (FCD) 23.253.4 and 23.253.5

We're aware of an issue affecting folder syncing in FileCloud Desktop (FCD) for customers running the above versions of FCD and FileCloud Server. A fix is now available in FCD version 23.253.6

What's happening

Consecutive folder renames or moves after the initial rename or move from FCD triggers a conflict resulting in renamed or moved folder and its contents not being synced to the server.

Renaming or moving a folder once from FCD works fine; it's specifically the second consecutive rename or move of that same folder, or new folder creation followed by a rename, that can cause it to enter a "sync pending" state and stop syncing. This is isolated to the specific folder involved — other files and folders will continue to sync normally.

Why this matters

If you log out of FCD while a folder is in this "sync pending" state, any changes made to that folder after the conflict occurred will be lost.

Fix

Upgrade FCD (Windows) to version 23.253.6.

What you need to do

1. Let FCD auto-update, or update manually, to version 23.253.6. DO NOT LOG OUT DURING OR IMMEDIATELY AFTER THE UPDATE.

2. Wait for the Activity feed to show the uploads and conflict copies(if any) for the previously affected folder.

3. Confirm in the FileCloud web UI that the folder and its content is present on the server.

4. Once confirmed, logout and log back in to reset the local state.

5. DO NOT LOG OUT BEFORE STEP 3, and do not confirm the "sync in progress" prompt for a folder whose content is not yet visible on the server.

What you may see after the upgrade and what you need to do

  • If you had a file renamed inside the affected folder: the folder may continue to show as "sync pending." Confirm the file is present and correct in the FileCloud web UI, then log out of FCD and log back in to reset the sync status.

  • If you edited a file inside the affected folder: a conflict copy (marked with your username) will be created. Review it and merge or delete as needed.

  • If you deleted the affected folder on the FileCloud web UI before upgrading: the folder will reappear on the web UI, empty. Delete it.

  • If the folder was renamed on the server to a different name than FCD's local one: you'll see two duplicate folders after upgrading. Review both and remove the outdated one.

Workaround if you're unable to upgrade to FCD 23.253.6

If you notice a folder stuck in a syncing state, do not log out of FCD — instead, duplicate the folder in FCD and wait for the duplicate to finish syncing before logging out.

Please contact FileCloud Support if further assistance is required.