Bucket Upload Not Open

bucket-upload-not-open · 409

The batch holds no upload in parts for this key, so the API signed no part and joined nothing.

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. A file over 16 MiB goes up in parts, and its upload opens when the file is signed.

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

Common causes

  • The file was never signed in this batch, or was signed as one piece because it is 16 MiB or less.
  • Its upload was completed or aborted already.

How to fix the call

  • Sign the file again with .../uploads to open its upload, then send its parts.
  • If it was completed, the file is in the bucket already: list the folder to check.

Example response

json
{
  "type": "bucket-upload-not-open",
  "title": "Bucket Upload Not Open",
  "detail": "Upload batch '0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402' has no open multipart upload for 'videos/launch.mp4'",
  "code": "BUCKET_UPLOAD_NOT_OPEN",
  "batchId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402",
  "key": "videos/launch.mp4",
  "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/parts",
  "method": "POST",
  "instance": "POST /v1/buckets/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/upload-batches/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/uploads/parts",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/bucket-upload-not-open"
}