Unverified50% confidenceDecision RuleExact time
For applications that need to detect incomplete responses, it is recommended to additionally check finishReason === 'interrupted' beyond existing error handling.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/22/2026
First Seen
Valid until: 1/20/2027
Sources
Related Entities
Related Claims
UnverifiedThe official patch notes include a Compatibility notice requiring applications that branch on finishReason to add an `interrupted` branch in switches, mapping tables, and custom validation.76% similarUnverifiedChecking response integrity should verify both that finish_reason is stop and that the key data structure matches expectations (e.g., items is a non-empty list).76% similarUnverifiedWhen a step fails, Resumate checks whether the same failure has occurred previously within the organization and reuses the resolution that worked last time.75% similarUnverifiedStreaming output combined with incremental validation can trigger an immediate alert or retry upon detecting finish_reason: length, without having to wait for the entire response to return.72% similarUnverifiedBefore upgrading to 2.0.81, search globally for exhaustive finish reason handling logic and confirm the newly added interrupted value is covered, to avoid CI type-check failures.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1086792API
curl https://kongchang.com/api/v1/knowledge/claims/1086792MCP
get_claim(id=1086792)