Unverified50% confidenceDecision RuleExact time
In LLM calls, client errors such as 400 (malformed request) and 401 (invalid key) should not trigger switching to a backup provider, because resending will only get the same error; only transient provider-side failures such as connection failures, timeouts, 429, and 5xx should trigger fallback.
1
Sources
50%
Confidence
Long-term
Relevance
10/15/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedError responses (such as 429 or 5xx) should never be cached, so that the next call can retry.69% similarUnverifiedRetrying all 5xx is not recommended, because 500 often represents a real server-side bug that will not self-heal within a short time, and failing fast exposes the problem.67% similarUnverifiedv3.20.0 clarified and supplemented error response documentation for several interfaces, including batch errors, file and upload errors, fine-tuning and model errors, and Responses not-found errors.65% similarUnverifiedRetries for free APIs should only target transient errors such as 429 and 503; other errors should be thrown directly to avoid blindly retrying code bugs.64% similarUnverifiedIn the ticket service failure demonstration, Catalyst reproduced the failure from a 96-request run and reduced it to a 16-request reproducer; the candidate fix achieved 0 errors out of 16, p99 of approximately 16ms, and passed all 3 holdout scenarios.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1040185API
curl https://kongchang.com/api/v1/knowledge/claims/1040185MCP
get_claim(id=1040185)