Not Abuse-Suspended
not-abuse-suspended · 409
An operator asked to lift an abuse suspension from something that isn't suspended for abuse, so nothing changed.
All pages
Only operators reach the routes that send it. subject is Billing account, Service environment or Bucket, id names it, and currentReason is the suspension it has, or null when it has none.
Besides the members every error carries, this type adds subject, id and currentReason.
- The account is suspended for
payment_failedorusage_limit, which money lifts, not this route. - It isn't suspended at all, or its suspension was already lifted.
- Read
currentReason: a payment suspension ends when billing reports the account in good standing with a way to pay, and a usage-limit one when the month's usage is back under the limit: a new month, or a raised or cleared limit. - Don't retry: these routes lift only an abuse suspension.
json
{
"type": "not-abuse-suspended",
"title": "Not Abuse-Suspended",
"detail": "Billing account '0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401' is suspended for 'payment_failed', which this endpoint may not lift. Only an abuse suspension can be resumed here.",
"subject": "Billing account",
"id": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
"currentReason": "payment_failed",
"requestId": "req-1785231000000-4f7b2c9ae",
"timestamp": "2026-07-28T09:30:00.000Z",
"path": "/v1/abuse/admin/account/resume",
"method": "POST",
"instance": "POST /v1/abuse/admin/account/resume",
"status": 409,
"docs": "https://ghaym.me/docs/errors/not-abuse-suspended"
}