Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.kash.bot/llms.txt

Use this file to discover all available pages before exploring further.

HTTP status: 503 · Title: “Service unavailable” · Retry-After: 30s

​
When it fires

A required external dependency (Postgres, Secrets Manager, Redis, blockchain RPC) is unreachable, and the route can’t degrade further. Distinct from INTERNAL_ERROR (which is “we don’t know what happened”) and ROUTE_DISABLED (which is “ops disabled this on purpose”).

​
Why it happens

  • Transient infrastructure blip (most common — clears in seconds).
  • Sustained dependency outage (visible on status.kash.bot).
  • A rare cascade where one dependency degraded and another can’t compensate.

​
How to fix

  • Honour Retry-After: 30 and back off with jitter. Most occurrences resolve within one retry.
  • If retries keep failing past 5 minutes, check the status page.
  • The TS SDK handles this automatically (KashServerError, retried with backoff up to its retry budget).