Bucket Provisioning

bucket-provisioning · 409

The bucket is still being created, so the API didn't delete it.

Deleting it now would leave an empty bucket behind that no one owns. The API takes the delete once the bucket is ready or has failed.

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

Common causes

  • The bucket was created moments ago and its status is still provisioning.

How to fix the call

  • Read the bucket with GET /v1/buckets/<id>, wait until its status is ready or failed, then delete it again.
  • If creating it stalls, the bucket reads as failed after 15 minutes and the delete goes through.

Example response

json
{
  "type": "bucket-provisioning",
  "title": "Bucket Provisioning",
  "detail": "Bucket '0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401' is still being created; delete it once it is ready or has failed",
  "code": "BUCKET_PROVISIONING",
  "bucketId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/buckets/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "method": "DELETE",
  "instance": "DELETE /v1/buckets/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/bucket-provisioning"
}