Service Suspended

service-suspended · 409

The service is suspended in this environment, so the API didn't start, deploy or roll it back.

The hold is the platform's, not the user's, and a start can't clear it. The service starts back on its own once the hold is lifted. environmentId names the environment where it is held.

Besides the members every error carries, this type adds serviceId and environmentId.

Common causes

  • A payment failed, or the account reached its usage limit, and the account's services were suspended with it.
  • An operator put the service on hold.

How to fix the call

  • Tell the user, quoting detail: settling the account lifts a failed-payment hold, raising the limit lifts a usage-limit one, and support lifts an operator's.
  • Don't start, deploy or roll back again until the hold is lifted: each is refused the same way.

Example response

json
{
  "type": "service-suspended",
  "title": "Service Suspended",
  "detail": "This service is suspended and cannot be started. Settle the account, or ask support to lift the hold, and it starts back on its own.",
  "serviceId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "environmentId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad403",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/start",
  "method": "POST",
  "instance": "POST /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/start",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/service-suspended"
}