Bucket Upload Incomplete

bucket-upload-incomplete · 409

The store doesn't hold every part of the file at its full size, so the API didn't join them.

These come from the upload routes the console's file browser calls; an app writing with its own S3 keys talks to the store and never meets them. The parts are read back from the store, never taken from the call. missingPartNumbers lists the parts that are missing or short, and the upload stays open for them.

Besides the members every error carries, this type adds code, key and missingPartNumbers.

Common causes

  • A part's upload failed or was cut off, such as on a dropped connection.
  • The upload was completed before every part had finished.

How to fix the call

  • Sign the parts in missingPartNumbers again with .../uploads/parts, send them, then complete again.
  • Don't complete again before those parts are sent: the answer will be the same.

Example response

json
{
  "type": "bucket-upload-incomplete",
  "title": "Bucket Upload Incomplete",
  "detail": "'videos/launch.mp4' is missing 2 part(s)",
  "code": "BUCKET_UPLOAD_INCOMPLETE",
  "key": "videos/launch.mp4",
  "missingPartNumbers": [
    3,
    7
  ],
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/buckets/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/upload-batches/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/uploads/complete",
  "method": "POST",
  "instance": "POST /v1/buckets/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/upload-batches/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/uploads/complete",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/bucket-upload-incomplete"
}