Errors

Uploaded file size does not match

After ingest, the on-disk or remote blob size does not match the expected file size.

Uploaded file size does not match

The product expected one byte size and found another on the final blob (often after SFTP ingest moves/copies from staging). Internal code may be final_blob_size_mismatch.

Why this happens

Staging file truncated, incomplete transfer into ingest, or remote object size ≠ session resolvedSizeBytes. Sibling of merge/stream mismatches on other paths (Uploaded size does not match declared size, part size mismatch, S3 size mismatch).

Diagnose and fix

1. For SFTP: check staging path, ingest worker logs, and that the client finished the put.

2. Confirm SFTP mod / ingest enabled on the server; retry a small test file.

3. Disk full or permission errors during move can yield short files — check the node.

4. Clean the failed session and re-upload.

Related

Uploaded file size does not match