Uploaded file exceeds maximum size
After parts landed, promote/finalize saw a remote (or stored) object larger than the declared totalBytes and refused to activate it.
Why this happens
Integrity check in finalizeUploadBlobOnStorageServer / promote paths: size drift, wrong object, or a partial duplicate that grew past the cataloged size. Different from the pre-upload “File exceeds your maximum upload size” plan cap — this is after bytes were written.
Diagnose and fix
1. Inspect the storage object size vs the pending file’s declared size; clean orphaned oversized objects if needed.
2. Still review Max upload size / Upload hard cap so clients cannot declare absurd sizes.
3. Retry a clean upload; avoid resuming into a corrupted remote key.
4. Check storage node health and logs around promote/complete.