Unverified50% confidenceOpinionExact time
When an agent repeatedly encounters 403 or 429 errors, standard tools throw them as recoverable exceptions, causing the LLM to retry repeatedly and trigger stricter blocking.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe tool should return a clear error message upon blocking (such as "all proxy nodes are currently rate-limited by the target host"), letting the LLM treat the failure as an unrecoverable state and thus switch strategies rather than retry.73% similarUnverifiedIn a failover architecture, a distinction should be made between errors worth retrying (429, 5xx, timeouts) and errors that should not be retried (400 parameter errors, 401 authentication failures).70% similarUnverifiedWhen LLM generation results fail validation and a retry is needed, resending the full context each time causes token consumption to expand rapidly.68% similarUnverifiedAPI异常中网关速率限制返回429错误，负载均衡器在后端不可用时返回502/503错误，GPU内存不足可能导致请求终止68% similarUnverifiedIn multi-agent systems, error propagation manifests as fault cascading; because LLMs tend to over-trust inputs (sycophancy), errors that enter the information flow are difficult for subsequent steps to correct on their own.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1016400API
curl https://kongchang.com/api/v1/knowledge/claims/1016400MCP
get_claim(id=1016400)