| Previous | Next |
| STATUS_CLOUD_FILE_PROVIDER_NOT_RUNNING | STATUS_CLOUD_FILE_METADATA_TOO_LARGE |
STATUS_CLOUD_FILE_METADATA_CORRUPT
This status concerns metadata attached to a local placeholder. Cloud Files keeps such information separately from the user-visible file bytes; it includes provider-supplied file identity and standard placeholder state. A damaged record can therefore affect open, hydrate, rename, or state operations even when the remote object still exists.
Do not treat this as a generic checksum failure of the document itself. Collect the placeholder path, file ID, sync-root file ID, provider identity, and the API operation that failed. Recovery should be performed by the provider using supported placeholder update, reversion, or re-enumeration logic rather than by modifying the reparse point by hand.
Useful checks
- Query placeholder information before attempting any recovery that could discard a locally modified version.
- Compare the provider's persistent mapping for this file with the local file identity returned in callbacks.
- Separate a corrupt placeholder record from a failed data-hydration or remote-version conflict.
Relevant documentation
- CfGetPlaceholderInfo describes placeholder identity, sizes, pin state, and in-sync state.
- Cloud Sync Engines describes the platform role in managing placeholders.
Looking for a different code? Search another status or error code.