Plan Full

database-cap-blocked · 402

The database can't start because the plan's compute cap is full, so the API opened no tunnel.

The cap's numbers come only when waking the database would pass the cap, and read as on plan-compute-cap-exceeded. A database the cap held at provisioning sends service and environment alone. The CLI exits with code 7.

Besides the members every error carries, this type adds service, environment, planKey, unit, capValue, currentTotal and projectedTotal.

Common causes

  • The database was held at provisioning because the plan had no room for it.
  • The call asked to wake the database, and waking it would put the account past its cap.

How to fix the call

  • Free room first: put another service to sleep, stop one, or choose a smaller size.
  • Or move to a plan with a higher cap: ghaym cloud billing set-plan --plan <key>. A plan change is the user's decision.
  • A database held at provisioning needs a retry once there is room. ghaym cloud services retry-provisioning <service> retries production only; for any other environment, send POST /v1/services/<id>/provisioning/retry?environmentId=<environment>.

Example response

json
{
  "type": "database-cap-blocked",
  "title": "Plan Full",
  "detail": "orders-db can't start: your plan is full.",
  "service": "orders-db",
  "environment": "staging",
  "planKey": "solo",
  "unit": "ram-gb",
  "capValue": 8,
  "currentTotal": 8,
  "projectedTotal": 9,
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/tunnels",
  "method": "POST",
  "instance": "POST /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/tunnels",
  "status": 402,
  "docs": "https://ghaym.me/docs/errors/database-cap-blocked"
}