| Previous | Next |
| STATUS_CLOUD_FILE_METADATA_CORRUPT | STATUS_CLOUD_FILE_PROPERTY_VERSION_NOT_SUPPORTED |
STATUS_CLOUD_FILE_METADATA_TOO_LARGE
Cloud Files metadata is not a place to store an arbitrary provider database. A sync provider supplies opaque identities for the sync root and placeholders, but the API documents explicit size limits for these values. Oversized identity or metadata payloads should be treated as a serialization-design error, not as a reason to truncate bytes until the call succeeds.
Measure the encoded byte length of every value passed to the platform, including version fields and binary wrappers. Keep only a stable key and compact schema version in the Cloud Files identity; retain large manifests, history, and provider-specific indexes in the provider's own storage.
Useful checks
- Log byte counts after serialization, not only source-string lengths.
- Verify that sync-root and file identities are bounded before registration or placeholder creation.
- Version compact identities explicitly so an upgrade can decode old records without embedding large compatibility data.
Relevant documentation
- CfRegisterSyncRoot documents identity fields and their maximum sizes.
- CfGetPlaceholderInfo shows how provider-supplied file identity is exposed by the platform.
Looking for a different code? Search another status or error code.