Unverified50% confidenceFactExact time
OpenAI identifies refusals and max-token truncation as two scenarios in which a response may not match the schema.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/11/2026
First Seen
Valid until: 1/9/2027
Sources
Related Entities
Related Claims
UnverifiedUsing exponential backoff retries to handle API request failures can avoid the avalanche effect caused by concentrated retries.70% similarUnverifiedIntroducing fuzzy semantic matching at the caching layer is essentially trading accuracy for performance, and may return incorrect answers that the user did not request.65% similarUnverifiedThere is a trade-off between showing the full rejection chain and presenting only the most likely root cause: the full chain is more informative but the report becomes verbose when there are many candidates, while the most likely cause is concise but can mislead users if the judgment is wrong.65% similarUnverifiedOpenAI 流式响应以 data: [DONE] 标记结束，Anthropic 则使用 event: message_stop 事件类型64% similarUnverifiedThe architecture uses a Relevance Gate mechanism: if the reranker does not find sufficiently relevant passages, the system directly returns an 'insufficient information' response rather than feeding weak context to the model.63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/998053API
curl https://kongchang.com/api/v1/knowledge/claims/998053MCP
get_claim(id=998053)