Unverified50% confidenceFactExact time
When Hard cap is enabled in TokenRouter, requests that exceed the limit are rejected with a 429 response until the period resets.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/11/2026
First Seen
Valid until: 1/9/2027
Sources
Related Entities
Related Claims
UnverifiedWhen an Access Token expires, the client should automatically use the Refresh Token to obtain a new token; if the automatic refresh process fails, the application will silently lose access to cloud data.57% similarUnverifiedv2.1.269 fixes an issue where the prompt cache was partially invalidated when a response was truncated upon hitting the output token limit and then automatically continued.56% similarUnverifiedFor scenarios using apiKeyHelper to return short-lived JWTs, expired cached tokens are refreshed before being sent, and 401/403 authentication errors are silently retried56% similarUnverifiedOAuth的long-lived refresh token可能在数月后静默失效，导致无头Agent在生产环境中断服务55% similarUnverifiedVersion 4.0.109 fixes the issue where replacement completion requests can maintain a loading state and be cancellable when an earlier request has already settled.55% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/998122API
curl https://kongchang.com/api/v1/knowledge/claims/998122MCP
get_claim(id=998122)