Unverified50% confidenceDecision RuleExact time
Meta's documentation specifies that when a 429 arrives, exponential backoff with jitter should be used, starting at about 500ms; if a Retry-After header is present, wait at least that long.
1
Sources
50%
Confidence
Long-term
Relevance
10/15/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen a 429 is received, exponential backoff with random jitter should be implemented starting at about 500ms, and if a Retry-After response header is present, wait at least that long; ignoring Retry-After or retrying at fixed intervals will prolong the outage for the entire team.77% similarUnverifiedIn LLM scenarios, latency hedging is the most commonly used strategy; in practice, the P50 or P75 latency value is typically used as the trigger threshold, and hedging is triggered if the first request has not returned its first token within the P75 time.62% similarUnverifiedRFC 6238 allows the server to tolerate a certain degree of drift, typically one 30-second window before and after, i.e. a tolerance range of about 90 seconds.60% similarUnverifiedThe retry loop in the code attempts at most 4 times, with exponential backoff starting at 500 milliseconds, and it prioritizes obeying the Retry-After response header when the service provides one.60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1034034API
curl https://kongchang.com/api/v1/knowledge/claims/1034034MCP
get_claim(id=1034034)