Instance Quota Exceeded

instance-quota-exceeded · 403

An operator already holds as many instances as the quota allows, so the API created no new one.

Instances are run by Ghaym's operators through the admin routes. limit is the quota, 2 by default; it is a standing limit, not a rate, so it is a 403 and not a 429.

Besides the members every error carries, this type adds userId and limit.

Common causes

  • Every slot in the quota holds an instance that isn't destroyed.

How to fix the call

  • Destroy an instance that is no longer needed, then retry.
  • Don't retry in a loop: the quota doesn't clear on its own.

Example response

json
{
  "type": "instance-quota-exceeded",
  "title": "Instance Quota Exceeded",
  "detail": "Instance limit of 2 reached; destroy an instance or contact support to raise it",
  "userId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "limit": 2,
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/admin/instances",
  "method": "POST",
  "instance": "POST /v1/admin/instances",
  "status": 403,
  "docs": "https://ghaym.me/docs/errors/instance-quota-exceeded"
}