Unverified50% confidenceFactExact time
HTTP 503 indicates temporary unavailability on the provider side and is usually unrelated to call frequency; 429 indicates the caller exceeded the per-unit-time quota, and the response headers often carry Retry-After. 503 is suited to exponential backoff retries, while 429 is better handled by switching to a backup model or deferring to the next period.
1
Sources
50%
Confidence
Long-term
Relevance
10/20/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIn 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.66% similarUnverifiedIf the server requests a wait longer than max_backoff, the client should give up rather than retry early, because retrying before Retry-After expires will escalate rate limiting into a ban.66% similarUnverifiedSetting maxRetries to 0 in generationConfig removes SDK-layer retries, so an endpoint that keeps returning 503 receives only 7 requests (about 74 seconds) before ending with [API Error: 503 upstream busy] and exit code 1.65% similarUnverifiedThe HTTP standard RFC 5861 defines the Cache-Control: stale-while-revalidate directive, which allows a cache to continue being used after expiration while asynchronously revalidating with the origin server in the background.65% similarUnverifiedv3.23.0 fixes issues in the responses module related to avoiding replay of indeterminate typed sends on reconnect (#4011) and respecting send queue limits during reconnection (#4000).62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1074232API
curl https://kongchang.com/api/v1/knowledge/claims/1074232MCP
get_claim(id=1074232)