| Previous | Next |
| ERROR_CLOUD_FILE_NOT_SUPPORTED | ERROR_CLOUD_FILE_READ_ONLY_VOLUME |
ERROR_CLOUD_FILE_INVALID_REQUEST
The operation conflicts with the placeholder state or sync-root policy
ERROR_CLOUD_FILE_INVALID_REQUEST means the platform rejected the requested cloud-file operation as invalid in its current context. One documented example is an ALWAYS_FULL hydration policy: operations that would produce a partially hydrated placeholder, including dehydration and some create, convert, or update calls, fail with this error.
Record the API, flags, file type, current placeholder state, and registered policies. Validate offset and length requirements for range operations and confirm that directory-only or file-only APIs are not being mixed. This status is normally deterministic; waiting for network recovery or restarting the provider will not repair invalid flags or an impossible state transition. Change the request or the sync-root policy rather than retrying blindly.
What to inspect
- Inspect hydration and population policy before create, convert, update, or dehydrate calls.
- Validate file-versus-directory requirements and all range parameters.
- Compare requested state transitions with current pin, hydration, and placeholder state.
References
- Microsoft: ALWAYS_FULL and other Cloud Files policies
- Microsoft: valid placeholder update options
- Microsoft: hydration range requirements
Looking for a different code? Search another status or error code.