Read Retry-After before repeating a rate-limited request

Interpret the actual response header

HTTP 429 identifies rate limiting; Retry-After is optional. HTTP defines its value as delay seconds or an HTTP date. A missing header does not mean immediate retries are safe. The times below are synthetic response examples.

Synthetic rate-limit responses
Response	Interpretation	Handling
429; Retry-After: 30	Wait at least 30 seconds from receipt	Schedule later, not a busy loop
429; HTTP-date value	Compare with reliable current time	Account for clock skew
429; header absent or invalid	Use documented fallback policy	Bound attempts and record the missing hint

Download editable CSV ↓

Coordinate the affected quota scope

Find whether the limit applies to a token, account, route or another documented scope. If ten workers all retry at the same instant, a single delay may only move the burst. Use a shared throttle and jitter that never shortens a valid minimum wait.

Can a random wait of 0–30 seconds satisfy Retry-After: 30?

Show the worked answer

No. Add any spreading delay after the required minimum, or use a policy that otherwise guarantees at least 30 seconds before another attempt.

Interpret the actual response header

Coordinate the affected quota scope

Related resources