Maximum number of retries beyond the initial attempt.
0 disables retries; 3 allows 1 initial + 3 retries = 4 total calls.
OptionalmaxLongest Retry-After this client will sleep through, in milliseconds.
Defaults to DEFAULT_MAX_RETRY_AFTER_MS.
A REST 429 asks for seconds and is worth waiting out. A HISTORY 429 is a
different animal: that budget is hourly, so a spent one can ask for most
of an hour, and honouring it up to max times means a process that sits
silent for hours and looks hung. Past this cap we do not sleep at all, and
throw RateLimitError carrying retryAfterMs so the caller can
checkpoint and come back.
If true, HTTP 429 responses are retried (honouring Retry-After).
OptionalrespectWait out a window the server has already said is spent.
When a response reports remaining: 0, the next request is a guaranteed
429 that also costs a unit of the caller's budget to be refused. Waiting
for the reset it advertised is strictly better than sending it. Setting
this false turns the client back into a purely reactive one.
Defaults to true.
Retry configuration for the Transport.
Semantics note:
maxis the number of retries beyond the initial attempt, not the total attempt count. A setting ofmax: 3means the transport will make up to 4 total calls (1 initial + 3 retries) before giving up. A setting ofmax: 0disables retries entirely and the transport will perform exactly one call.