11/Documentation/Error Handling
11/Error Handling
Response Codes & Retry Policy
Proxy errors are surfaced as standard HTTP status codes on the upstream response. Always implement exponential backoff with jitter; never retry tighter than 250 ms on a 429 or you will compound the rate limit. Persistent 5xx responses should trigger a fresh sticky session before the next retry.
407
Proxy Authentication Required
Credentials missing or revoked. Rotate from the dashboard.
429
Rate Limited
Concurrency cap exceeded. Back off with exponential jitter (base 250 ms).
502
Bad Gateway
Upstream target rejected. Retry on a fresh sticky session.