| Previous | Next |
| ERROR_CLOUD_FILE_METADATA_CORRUPT | ERROR_CLOUD_FILE_PROPERTY_BLOB_TOO_LARGE |
ERROR_CLOUD_FILE_METADATA_TOO_LARGE
The metadata attached to the placeholder no longer fits platform limits
ERROR_CLOUD_FILE_METADATA_TOO_LARGE indicates a size failure in cloud-file metadata rather than the ordinary file content. CFAPI carries an opaque provider-supplied FileIdentity and platform information for each placeholder. The identity is returned to provider callbacks and should normally be a compact stable key, not a serialized copy of the complete remote object or account record.
Measure the exact identity and metadata buffers passed to placeholder creation or update. If a provider recently changed its identity schema, compare new and old formats and confirm that accidental payload growth, duplicate fields, or unbounded path data was not introduced. Store large mutable metadata in the provider database or remote service and keep the placeholder identity small enough to locate that record. Retrying with the same oversized buffer cannot succeed.
What to inspect
- Log FileIdentityLength and all metadata-buffer lengths at create and update calls.
- Check for schema migrations that copied remote metadata into the opaque identity blob.
- Use a compact stable identifier and keep larger state in provider-managed storage.
References
- Microsoft: FileIdentityLength in placeholder information
- Microsoft: CFAPI placeholder creation
- Microsoft: placeholder metadata and identity updates
Looking for a different code? Search another status or error code.