Exposure Ceiling Exceeded
exposure-ceiling-exceeded · 402
This month's usage has reached the ceiling billing set on what the account may owe, so the API started nothing new.
All pages
It isn't the usage limit the account sets itself: billing sets this one, and only settling what is open, or support raising it, moves it. It also refuses what adds capacity with no deploy: a new environment in a project that has a database, a published changeset that adds a database copy or raises replicas or readers, a database resize to more memory, and a provisioning retry. The amounts are strings in currency, with that currency's decimals: three for JOD, two for SAR.
Besides the members every error carries, this type adds currency, usageJod, exposureCeilingJod and billingUrl.
- The account used as much this month as billing lets it owe, and a launch, a deploy, a start, a wake or a change that adds capacity would add more.
- Tell the user to settle what is open at
billingUrl, or to contact support to raise the ceiling. Both are theirs to do. - Services already running keep running: only new usage is refused.
- Don't retry until what is open is settled: the answer won't change.
json
{
"type": "exposure-ceiling-exceeded",
"title": "Exposure Ceiling Exceeded",
"detail": "This month's usage (250.000 JOD) has reached the 250.000 JOD exposure ceiling on this account. Settle the open balance at https://auth.ghaym.me/account/billing, or contact support to have the ceiling raised.",
"currency": "JOD",
"usageJod": "250.000",
"exposureCeilingJod": "250.000",
"billingUrl": "https://auth.ghaym.me/account/billing",
"requestId": "req-1785231000000-4f7b2c9ae",
"timestamp": "2026-07-28T09:30:00.000Z",
"path": "/v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/deployments",
"method": "POST",
"instance": "POST /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/deployments",
"status": 402,
"docs": "https://ghaym.me/docs/errors/exposure-ceiling-exceeded"
}