Bucket Quota Reached

bucket-quota-reached · 409

The bucket filled up while the file was uploading, so the store refused it and nothing of the file was kept.

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. It comes when the parts of a file over 16 MiB are joined, and the upload is aborted with it. It is a 409, not a 403: the bucket's state is at fault, not the caller's seat.

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

Common causes

  • The app wrote to the bucket at the same time and used the last of its room.
  • The bucket was nearly full before the upload started.

How to fix the call

  • Free room by deleting files the user no longer needs, if they agree, then upload the file again from the start.
  • Or give the account's buckets more room on a bigger plan: ghaym cloud billing set-plan --plan <key>. A plan change is the user's decision.
  • Don't complete the upload again: it is gone, so start a new one.

Example response

json
{
  "type": "bucket-quota-reached",
  "title": "Bucket Quota Reached",
  "detail": "Bucket '0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401' has no room left for 'videos/launch.mp4'; nothing of it was kept",
  "code": "BUCKET_QUOTA_REACHED",
  "bucketId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "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/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-quota-reached"
}