When a request is limited
A limited HTTP request returns429 Too Many Requests and Retry-After when the transport supports it. Successful Search API responses also advertise the current limit, remaining requests, and reset window.
Retry safely
- Respect
Retry-After. - Use exponential backoff with jitter.
- Cap retry count and maximum delay.
- Debounce interactive Search input.
- Cache identical read-only requests for an appropriate interval.
- Reuse the same
requestIdwhen retrying the same Action mutation.
400, 401, 403, or 404 without changing the request, credential, or authority.
Never generate a new Action
requestId merely because the transport failed. A changed ID can create duplicate work.