upstream_failed

What it means

A service BlueBot depends on failed.

Common causes

• File storage or email didn’t answer.

What to do

A service BlueBot depends on failed. 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

{
  "error": {
    "code": "upstream_failed",
    "message": "File storage didn’t answer.",
    "hint": "A service BlueBot depends on failed. Try again shortly.",
    "doc_url": "https://usebluebot.com/docs/errors/upstream_failed",
    "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

• Errors: the envelope and every code
• Idempotency: retrying without sending twice
• Limits: every cap and what happens when you reach it