| Previous | Next |
| STATUS_NOT_A_CLOUD_FILE | STATUS_CLOUD_FILE_ALREADY_CONNECTED |
STATUS_CLOUD_FILE_NOT_IN_SYNC
The in-sync flag is a local Cloud Files state, not a successful network test. The platform can clear it when data changes, and the provider sets it again only after it has reconciled the local version with its own remote state. A file may therefore be fully hydrated yet still be out of sync.
A provider should not set the state back optimistically. When an upload, merge, or metadata update completes, use the USN-aware form of CfSetInSyncState so a local change made during the final step is not accidentally marked synchronized.
Useful checks
- Capture the local USN, in-sync state, and provider revision before beginning a reconciliation.
- Distinguish an out-of-sync marker from authentication, network, and validation failures.
- Clear or set the state through the documented API instead of changing file attributes directly.
Relevant documentation
- CfSetInSyncState documents the state transition and USN race protection.
- CF_SYNC_POLICIES explains when the platform clears in-sync state.
Looking for a different code? Search another status or error code.