AniLink - v2.0.0
    Preparing search index...

    Interface RetryPolicy

    Retry policy for transient transport failures.

    Delays between retries use exponential backoff with full jitter by default: each wait is a random value between 0 and the computed exponential cap so concurrent clients do not synchronize their retries (thundering herd). Server-dictated Retry-After delays are never jittered.

    interface RetryPolicy {
        baseDelayMs: number;
        jitter?: boolean;
        maxDelayMs: number;
        maxRetries: number;
        retryOnNetworkError: boolean;
        retryOnStatus: readonly number[];
    }
    Index
    baseDelayMs: number

    The base delay before the first retry, in milliseconds.

    jitter?: boolean

    Whether to apply full jitter to computed backoff delays. Defaults to true.

    maxDelayMs: number

    The maximum delay between retries, in milliseconds.

    maxRetries: number

    The maximum number of retries after the initial attempt.

    retryOnNetworkError: boolean

    Whether network and timeout failures trigger a retry.

    retryOnStatus: readonly number[]

    HTTP status codes that trigger a retry.