Retry Policy
When and how failed requests are retried. The defaults match the official JS SDK: two retries, 0.5 s backoff doubling to a 5 s cap with up to 25% subtracted as jitter, and server retry-after-ms / Retry-After hints honored up to maxRetryAfter. The Python SDK shares the retries, backoff and statuses but doesn't cap hints, and adds a 30 s budget per call, which jev4k doesn't have: timeout applies per attempt.
Java can't call the full constructor or copy, whose Duration parameters Kotlin hides from it. It starts from the no-argument new RetryPolicy() and changes one setting at a time with the with… methods, which take milliseconds: new RetryPolicy().withMaxRetries(4).withInitialBackoffMillis(250). To move both backoff limits, use withBackoffMillis, which checks them together.
Constructors
Properties
Functions
A copy with both initialBackoff and maxBackoff changed, in milliseconds. Changed one at a time, they can fail on the way, when a new value passes the other's old one.
A copy with initialBackoff changed, in milliseconds.
A copy with jitter changed.
A copy with maxBackoff changed, in milliseconds.
A copy with maxRetries changed.
A copy with maxRetryAfter changed, in milliseconds.
A copy with respectRetryAfter changed.
A copy with retryOnConnectionError changed.
A copy with retryOnTimeout changed.
A copy with retryStatuses changed.