Unverified50% confidenceCautionExact time
Some relay providers still return HTTP 200 when the upstream rate-limits them, their balance is exhausted, or the model is unavailable, and embed the error information in the response body rather than the standard choices structure.
1
Sources
50%
Confidence
Long-term
Relevance
10/11/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedAfter stream resumability is removed, when a long streaming response encounters a network interruption the client can only re-issue the complete request, potentially wasting compute resources and causing inconsistency between the two results.71% similarUnverifiedAn API returning 200 OK does not necessarily mean the data has been persisted on all replicas, especially in architectures that use asynchronous write queues, multi-level caching, or cross-region replication.68% similarUnverifiedAn API call that returns status code 200 but loses a critical field is still considered a failure under the contextual reliability evaluation framework.66% similarUnverifiedThe fix is to locate the Log Response Data option under the Response section of the HTTP Request node and switch it to Never.66% similarUnverifiedEven if the interface returns 200, the absence of a corresponding database change is insufficient to prove that the business operation completed successfully.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/998884API
curl https://kongchang.com/api/v1/knowledge/claims/998884MCP
get_claim(id=998884)