GitHubLog in
Start here

upstream_unavailable · 5101 · HTTP 502

The transcript service could not be reached. Safe to retry.

Number5101
HTTP status502Bad Gateway
Familytransient5xxx · transient, retry with backoff

Example response

JSON
{
  "ok": false,
  "request_id": "req_…",
  "error": {
    "code": "upstream_unavailable",
    "number": 5101,
    "message": "The transcript service could not be reached. Safe to retry.",
    "docs": "https://transcriptfetch.com/docs/errors/upstream_unavailable"
  }
}

Every failure carries error.code, error.number, error.message and error.docs, plus at most one of retry_with (the request change that would succeed), details (structured specifics) or issues (validation problems).

What it means

The transcript service could not be reached. Safe to retry.

Why it happens

  • The transcript service behind the API was briefly unreachable.
  • The idempotency store was unavailable, so a request with an Idempotency-Key was refused rather than risk double-billing (HTTP 503 in that case).

What to do

  • Retry with exponential backoff; these are transient by nature.
  • Check status at status.transcriptfetch.com if failures persist.
Retryable? Yes, safe to retry; failed requests are never charged. Every error response carries a request_id; include it when contacting support.