Unverified50% confidenceFactExact time
In the prototype, triggering the message budget or the recipient cap immediately returns a 402 error, and once the kill switch is enabled all send requests return 503.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/18/2026
First Seen
Valid until: 1/16/2027
Sources
Related Entities
Related Claims
UnverifiedIn 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.68% similarUnverifiedError responses (such as 429 or 5xx) should never be cached, so that the next call can retry.64% similarUnverifiedAfter setting DFLASH_TOKENS=15, in citation requests with a 20k context it causes the engine to crash, reporting EngineDeadError and a marlin_gemm allocation failure, after which every request returns 500 and it cannot self-recover.63% similarUnverifiedv2.1.258 fixed the issue in remote sessions and scheduled sessions where failed re-sending of permission approvals threw a 'user messages must have non-empty content' error, causing session failures.63% 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.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1062793API
curl https://kongchang.com/api/v1/knowledge/claims/1062793MCP
get_claim(id=1062793)