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
- Validate API key value
- Validate
Authorization: Bearer ...format - Restart bot after
.envupdates
429 Rate limit
- Apply backpressure in caller
- Review per-tenant limits
- Retry with jitter
Timeout
- Lower
max_tokens - Route heavy tasks to remote fallback
- Reassess local model profile