Bucket Upload Batch Closed

bucket-upload-batch-closed · 409

The upload batch has ended, so the API signs nothing more under it.

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 batch groups the files of one upload. The batch's state shows in detail only: the API writes the HTTP status into status over it.

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

Common causes

  • The batch was completed already, by this client or another tab.
  • Its last signed URL expired with the batch still open, and the sweep ended it.
  • Another call is completing the batch right now: detail then says closing.

How to fix the call

  • Start a new batch with POST /v1/buckets/<id>/upload-batches, and sign the files still to go under it.
  • What already landed is kept and recorded: list the folder before uploading a file again.

Example response

json
{
  "type": "bucket-upload-batch-closed",
  "title": "Bucket Upload Batch Closed",
  "detail": "Upload batch '0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402' is expired; start a new one",
  "code": "BUCKET_UPLOAD_BATCH_CLOSED",
  "batchId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402",
  "status": 409,
  "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",
  "method": "POST",
  "instance": "POST /v1/buckets/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/upload-batches/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/uploads",
  "docs": "https://ghaym.me/docs/errors/bucket-upload-batch-closed"
}