Skip to content

cooldown_active

Cooldown active. HTTP status 409 or 429.

Something recent blocks this action for now. Three cases return it: a recent reinstall of the same server, a domain still locked after a recent registration or transfer, or an unpaid earlier critical credit invoice.

What to do

Read recovery.action in the response. For await_cooldown, wait for the seconds in the Retry-After header when present (a reinstall waits up to five minutes), then retry. For pay_outstanding_invoice, pay or cancel the invoice in invoice.id first.

What the message says

  • example.com: The domain is within the post-registration transfer lock window.

Example

Response 429
{
"type": "https://developer.hostup.se/errors/cooldown_active",
"title": "Cooldown active",
"status": 429,
"detail": "example.com: The domain is within the post-registration transfer lock window.",
"code": "cooldown_active",
"requestId": "req_01hxa3b4c5d6e7f8g9h0j1k2m3"
}

Branch on code, not on title or detail. When you contact support about it, include the requestId. More in Errors and retries.

Endpoints that return it