| Previous | Next |
| STATUS_CLOUD_FILE_NOT_UNDER_SYNC_ROOT | STATUS_CLOUD_FILE_PINNED |
STATUS_CLOUD_FILE_IN_USE
An active cloud file can have open handles, pending user I/O, hydration work, or a provider callback that makes a destructive state change unsafe. This status is about operation ordering; it does not prove that the file is corrupt or that the provider account is unavailable.
Identify the operation that needs exclusivity and wait for the appropriate close, cancellation, or completion boundary. For a sync engine, that normally means tracking requests by file identity and transfer/request keys rather than inferring idleness only from the visible File Explorer window.
Useful checks
- Capture the current callback type, file identity, request key, and outstanding transfer state.
- Use close-completion and cancellation notifications to retire provider work safely.
- Avoid forcibly terminating user processes merely to perform a routine placeholder update.
Relevant documentation
- CF_CALLBACK_PARAMETERS documents fetch, cancel, open, and close callback data.
- CfConnectSyncRoot describes the callback channel owned by the provider.
Looking for a different code? Search another status or error code.