| Previous | Next |
| ERROR_CLOUD_FILE_IN_USE | ERROR_CLOUD_FILE_REQUEST_ABORTED |
ERROR_CLOUD_FILE_PINNED
The operation conflicts with the user's keep-local intent
ERROR_CLOUD_FILE_PINNED reflects the placeholder pin state. CFAPI defines pinning as user intent, and any application can set it with CfSetPinState when access permits. A pinned placeholder is expected to remain available locally, so dehydration or another operation that discards local content can be rejected.
Query the current PinState rather than inferring it only from shell icons. Confirm whether the action is user initiated, provider policy driven, or part of automatic space management. If local data must be released, first obtain an explicit unpin decision and allow the normal state transition; do not silently override pinned intent. Pin state is also separate from in-sync state, so unpinning does not prove that local modifications have been uploaded.
What to inspect
- Read PinState from placeholder information before dehydration.
- Preserve explicit user intent across provider restarts and recursive operations.
- Confirm the file is in sync before removing locally available data.
References
- Microsoft: pin state represents user intent
- Microsoft: PinState and InSyncState are separate fields
- Microsoft: auto-dehydration and pin behavior
Looking for a different code? Search another status or error code.