| Previous | Next |
| STATUS_CLOUD_FILE_IN_USE | STATUS_CLOUD_FILE_REQUEST_ABORTED |
STATUS_CLOUD_FILE_PINNED
A pinned state represents user intent that a placeholder remain locally available. It is independent of whether the file is currently in sync, and any application—not only the sync provider—can set it. Operations that need to dehydrate or otherwise remove local availability must respect that intent.
Do not silently override a pin just to reclaim space or complete a provider cleanup task. Inspect the file's pin and in-sync states, then request or apply an explicit unpin transition through the documented API before scheduling a compatible dehydration operation.
Useful checks
- Distinguish a pin-state conflict from an active handle conflict or a validation failure.
- For directories, use recursive pin flags only when the desired user-visible scope is clear.
- Preserve pinned availability across provider restart and reconnect instead of reconstructing it from remote metadata alone.
Relevant documentation
- CfSetPinState defines pin state as user intent and documents recursive changes.
- CfGetPlaceholderInfo exposes pin state and in-sync state for a placeholder.
Looking for a different code? Search another status or error code.