Unverified50% confidenceCautionExact time
For LLM calls, 5xx errors and timeouts are worth retrying, while retrying 400-class errors is usually meaningless; retrying requests with side effects may cause duplicate billing, so idempotency keys or request deduplication should be incorporated into the design.
1
Sources
50%
Confidence
Long-term
Relevance
10/27/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedRetrying 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.75% similarUnverifiedIn 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.69% similarUnverifiedMitigating prompt drift requires pinning the LLM version and parameters, recording the full prompt and response for every step, and running regression tests; but silent updates from model vendors and changes in tool return formats also cause drift, so prompts, model versions, parameters, and tool schemas should be versioned together as one set of immutable configuration.68% similarUnverifiedTest drift makes scores incomparable, so you must lock the task set version and prompt version, and record the model ID rather than "latest version".65% similarUnverifiedWhen encountering rate-limiting errors, one should not continuously retry to reset the window; staggering request times allows for continued usage.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1104101API
curl https://kongchang.com/api/v1/knowledge/claims/1104101MCP
get_claim(id=1104101)