| Previous | Next |
| STATUS_CLOUD_FILE_ALREADY_CONNECTED | STATUS_CLOUD_FILE_INVALID_REQUEST |
STATUS_CLOUD_FILE_NOT_SUPPORTED
Cloud Files capabilities are negotiated through the sync root's policies and the operations implemented by the provider. For example, a root with an ALWAYS_FULL hydration policy cannot perform an operation that would leave a placeholder partially hydrated. A provider may also decline a callback or operation it does not implement.
This is not normally a transient connectivity failure. Diagnose the requested operation, current hydration and population policies, platform version, and provider feature set. Changing retries or waiting for network recovery will not make a deliberately unsupported operation valid.
Useful checks
- Log the exact
CF_OPERATION_TYPE, placeholder state, and policy active for the root. - Check whether the operation requires a different hydration policy or an optional provider callback.
- Offer a supported workflow, such as fully hydrating the file before an operation that cannot run on a placeholder.
Relevant documentation
- CF_SYNC_POLICIES documents hydration-policy effects and unsupported placeholder transitions.
- CF_OPERATION_PARAMETERS documents the provider operations used for hydration and validation.
Looking for a different code? Search another status or error code.