An Error Map You Can Use While Debugging
Understand how to classify and handle common HTTP error codes encountered in LLM API calls. Explore practical steps to diagnose issues related to request formatting, authentication, rate limiting, and transient server failures. Learn to apply targeted fixes, implement retry logic, and maintain clear run logs for efficient debugging and workflow reliability.
2026-08-19T10:14:03Z POST /v1/triage -> HTTP 401 Unauthorized
That single 401 line already narrows the first fix. The request reached an HTTP endpoint that returned an authentication failure, so the first checks should be the credentials and permissions rather than the request body. A 401 response alone does not prove that the request reached the model provider directly because a gateway or proxy can also return it.
This builds a small map from status code family to cause class to first action, so a run history line points ...