unavailable
503 Unavailable. BlueBot isn’t taking requests right now, during maintenance or an incident.
| Status | Code | Retry? |
|---|---|---|
| 503 Unavailable | unavailable | Yes, after waiting |
What it means
BlueBot isn’t taking requests right now, during maintenance or an incident. GET /v1/status says what is going on.
Common causes
- Maintenance.
- The database is unreachable.
What to do
BlueBot is not taking requests right now. Try again shortly.
Can I retry it?
Yes, after waiting. Wait the seconds in retry_after (or the Retry-After header) when the answer has them, otherwise back off from a second or two. With the same Idempotency-Key, a retried send never sends twice.
What the answer looks like
Response503
{
"error": {
"code": "unavailable",
"message": "BlueBot isn’t taking requests right now.",
"hint": "BlueBot is not taking requests right now. Try again shortly.",
"doc_url": "https://usebluebot.com/docs/errors/unavailable",
"request_id": "req_1Hq2LxW9cVbN3mKpRtYs0a"
}
}Branch on code, which never changes. message and hint are written for people and may be reworded. Quote request_id when you write to support.
Related
- : the envelope and every code
- : retrying without sending twice
- : every cap and what happens when you reach it