Windows error 377 (ERROR_CLOUD_FILE_NOT_IN

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: the placeholder is marked as having unsynchronized changes.

Could be also:
Constant	Type	OS
CLUSTER_CLUSPORT_STATUS_IO_TIMEOUT_LIVEDUMP	BugCheck Code	Windows

Previous	Next
ERROR_NOT_A_CLOUD_FILE	ERROR_CLOUD_FILE_ALREADY_CONNECTED

ERROR_CLOUD_FILE_NOT_IN_SYNC

The local placeholder state is not confirmed against the cloud

ERROR_CLOUD_FILE_NOT_IN_SYNC reflects the CFAPI in-sync state, which is separate from hydration and pin state. A file can be fully hydrated yet not in sync because local data or tracked metadata changed. Conversely, a dehydrated placeholder can be in sync if its cloud identity and local namespace state match the provider's authoritative version.

Query CF_PLACEHOLDER_STANDARD_INFO and inspect InSyncState, ModifiedDataSize, and the provider's upload journal. After successfully uploading changes, use CfSetInSyncState with the relevant USN when possible so that a concurrent local write cannot be incorrectly acknowledged. Pinning or hydrating the file does not upload it and should not be used as a substitute for synchronization.

What to inspect

Compare InSyncState with provider upload status and ModifiedDataSize.
Use the USN guard when setting in-sync state after an upload.
Do not treat hydrated, pinned, and in-sync as interchangeable states.

References

Looking for a different code? Search another status or error code.