> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aicord.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Common errors

# <img src="https://mintcdn.com/lipedevv/MuqSig17BRwFcVpd/icons/troubleshoot.svg?fit=max&auto=format&n=MuqSig17BRwFcVpd&q=85&s=bca67852c4813f210a46becbffe2680c" alt="Troubleshooting icon" width="22" data-path="icons/troubleshoot.svg" /> Troubleshooting

Quick diagnosis for common AiCordCloud failures.

| Error                | Typical cause                  | Immediate fix                                        |
| -------------------- | ------------------------------ | ---------------------------------------------------- |
| `401 Unauthorized`   | Wrong or rotated key           | Validate key and auth header, then restart bot       |
| `429 Rate limit`     | Burst too high                 | Reduce burst, increase tenant limits, queue requests |
| `Timeout`            | CPU saturation or long prompts | Reduce tokens and route heavy prompts to fallback    |
| `502 Upstream`       | Upstream unavailable           | Verify upstream process, URL, key, and failover      |
| Billing/quota errors | No credits                     | Refill billing and confirm provider account status   |

## 401 Unauthorized

1. Validate API key value
2. Validate `Authorization: Bearer ...` format
3. Restart bot after `.env` updates

## 429 Rate limit

1. Apply backpressure in caller
2. Review per-tenant limits
3. Retry with jitter

## Timeout

1. Lower `max_tokens`
2. Route heavy tasks to remote fallback
3. Reassess local model profile