Bucket Across Sites

bucket-across-sites · 422

The bucket and the service are in different sites, so the API refused the change.

A bucket connects only to a service in its own site. detail names the bucket and the service, each with its site. The API checks the sites again when you apply, so the refusal can come then too.

Besides the members every error carries, this type adds code, service, serviceSite, target and targetSite.

Common causes

  • The bucket is in another site than the service.
  • A variable that refers to the bucket's key, saved on a service in another site, gets the same refusal.

How to fix the call

  • Connect a bucket that is in the service's own site.

Example response

json
{
  "type": "bucket-across-sites",
  "title": "Bucket Across Sites",
  "detail": "assets-sa is in riyadh-1 and web is in amman-1. A bucket connects only to a service in its own site.",
  "code": "bucket_across_sites",
  "service": "web",
  "serviceSite": "amman-1",
  "target": "assets-sa",
  "targetSite": "riyadh-1",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/environments/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/changeset/entries",
  "method": "PUT",
  "instance": "PUT /v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/environments/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/changeset/entries",
  "status": 422,
  "docs": "https://ghaym.me/docs/errors/bucket-across-sites"
}