kex docs Standard Library

Control.Retry

module Control.Retry

Runs bounded retries with a reusable schedule.

Retry.run executes the block immediately. An Ok stops the run; an Error schedules another attempt. When attempts or total sleep run out, the last error is returned unchanged. Runtime faults are not caught.

HTTP responses, including 429 and 503, are Ok(response). Automatic retries handle request failures, not response statuses. Use again and done to classify responses or stop on permanent errors. Repeat writes only when the application makes them safe, for example with idempotency keys. A schedule bounds retry sleep, not the operation's execution time; configure request timeouts separately.

Examples

Retry a request and handle the final result

using Control.Retry
using Net.HTTP

let result = Retry.run(attempts: 5) do
  HTTP.get("https://api.example.com/inventory")
end
match result do
  Ok(response) => IO.printLine(response.status.code)
  Error(error) => IO.printLine(error.message)
end

module Control.Retry.Retry

Provides automatic error retries and explicit retry decisions.

again

again(value: X) -> Decision<X>

Requests another attempt if the schedule allows it.

Parameters
value
the last outcome, retained if the schedule is exhausted

Returns Again(value)

Examples

Polling an application job

Retry.again("pending")

done

done(value: X) -> Decision<X>

Stops immediately, even when the application value represents failure.

Parameters
value
the final application outcome

Returns Done(value)

Examples

Stop on invalid credentials without retrying

Retry.done(Error("invalid credentials"))

run

run : Block<X> -> Schedule -> Integer -> Duration -> Float -> Duration -> Float -> Duration? -> (Duration -> Void) -> Block<Float> -> (Info<X> -> Void) -> X

Runs a fresh operation until it succeeds, stops, or exhausts its schedule.

The first attempt is immediate. Every later attempt follows one sleep. There is no sleep after success or the final error. Named timing options override the corresponding schedule field for this execution only.

An ordinary block returns Result<X, E>: Ok stops, Error retries, and exhaustion returns the last Error unchanged. An explicit block returns Decision<X>: Done stops, Again retries, and exhaustion returns the last Again. Match the returned decision to distinguish completion from exhaustion. Use one form consistently within a block.

Finite settings are normalized: attempts below one become one, negative durations become zero, backoff below one becomes one, jitter and random samples are clamped to 0..1. Non-finite Float settings are unsupported.

Done(Error(...)) means the application stopped on a permanent error. Again(Ok(response)) means an unacceptable HTTP status persisted until exhaustion. HTTP status classification and Retry-After handling are the application's responsibility; run has no HTTP-specific behavior.

The testing hooks are independent: replacing sleep keeps normal random sampling, and replacing randomness keeps real sleep. A random sample of 0 selects the lower jitter bound, 0.5 the base, and 1 the upper bound. With zero jitter no random sample is needed. lint:allow parameter-count — named options make each setting independent

Parameters
operation
fresh Result or Decision on each attempt
schedule
reusable settings; defaults to Schedule {}
attempts
total attempts; defaults to the schedule field
delay
initial wait; defaults to the schedule field
backoff
delay multiplier; defaults to the schedule field
maximumDelay
sleep cap; defaults to the schedule field
jitter
variation fraction; defaults to the schedule field
maximumTotalDelay
sleep budget; defaults to the field
sleeper
defaults to real Task.sleep
random
defaults to secure backend sampling in 0..1
onRetry
reports an allowed retry; defaults to no action

Returns first Ok/Done or last Error/Again, without extra wrapping

Examples

Named options without constructing a schedule

Retry.run(attempts: 5, delay: 200.milliseconds, jitter: 0.0) do
  Ok("ready")
end
# => Ok("ready")

Stop before a wait exceeds the total sleep budget

Retry.run(
  attempts: 5, delay: 1.seconds, backoff: 2.0,
  jitter: 0.0, maximumTotalDelay: Just(2.seconds)
) do
  Error("busy")
end
# => Error("busy"), two calls and one second of sleep

Test jitter without waiting

Retry.run(
  attempts: 2, delay: 4.seconds, jitter: 0.25,
  sleeper: { |wait| Assert.equal(wait, 3.seconds) },
  random: { 0.0 }
) do
  Error("temporary")
end
# => Error("temporary"), two calls and one fake sleep

Report progress to a user or log

using Net.HTTP
Retry.run(attempts: 5, onRetry: { |info|
  let progress = "retrying ${info.nextAttempt}/${info.maximumAttempts}"
  IO.printLine("${progress} in ${info.delay.seconds} seconds")
}) do
  HTTP.get("https://api.example.com/inventory")
end

Retry temporary HTTP failures and selected statuses

using Net
using Net.HTTP
let schedule = Retry.Schedule { attempts: 5 }
let outcome = Retry.run(schedule: schedule) do
  let result = HTTP.get("https://api.example.com/inventory")
  match result do
    Error(error) => if error.kind == Timeout || error.kind == Connect
      Retry.again(result)
    else
      Retry.done(result)
    end
    Ok(response) => if [429, 502, 503, 504].contains?(response.status.code)
      Retry.again(result)
    else
      Retry.done(result)
    end
  end
end
match outcome do
  Done(result) => IO.printLine(result)
  Again(last) => IO.printLine("retry budget exhausted: ${last}")
end

record Schedule

Describes the timing and limits of one execution of run.

All fields are optional. Defaults allow three attempts with exponential backoff from 100 milliseconds, capped at 5 seconds, with 20% jitter. Creating a schedule performs no work. It is immutable configuration: each run starts a fresh attempt count and delay sequence.

  • attempts: maximum executions, including the first; default 3. * delay: initial base wait; default 100 milliseconds. * backoff: base-delay multiplier; default 2.0, or 1.0 for fixed waits. * maximumDelay: cap on each actual wait, including jitter; default 5 seconds. * jitter: symmetric proportional variation; default 0.2, or 0.0 to disable. * maximumTotalDelay: cumulative sleep allowance; default None. Operation execution time is excluded. A wait that exceeds the remaining allowance ends the run without sleeping or calling the operation again.
Examples

Fixed delays: three waits of 250 milliseconds

let schedule = Retry.Schedule {
  attempts: 4, delay: 250.milliseconds, backoff: 1.0,
  maximumDelay: 250.milliseconds, jitter: 0.0
}
Retry.run(schedule: schedule) do
  Error("not ready")
end
# => Error("not ready"), after four calls and 750 ms of sleep

Exponential delays: 200, 400, 800, 1600 milliseconds

let schedule = Retry.Schedule {
  attempts: 5, delay: 200.milliseconds, backoff: 2.0,
  maximumDelay: 5.seconds, jitter: 0.0
}
Retry.run(schedule: schedule) do
  Ok("ready")
end
# => Ok("ready"), immediately, without sleeping

Capped delays: 500 ms, 1 s, 2 s, 2 s, 2 s

Retry.Schedule {
  attempts: 6, delay: 500.milliseconds, backoff: 2.0,
  maximumDelay: 2.seconds, jitter: 0.0
}

Share settings, not an attempt budget

using Net.HTTP
let schedule = Retry.Schedule { attempts: 5 }
let inventory = Retry.run(schedule: schedule) do
  HTTP.get("https://api.example.com/inventory")
end
let orders = Retry.run(schedule: schedule) do
  HTTP.get("https://api.example.com/orders")
end
# Each request gets up to five attempts, independently.

Fields

attempts
Integer optional
delay
Duration optional
backoff
Float optional
maximumDelay
Duration optional
jitter
Float optional
maximumTotalDelay
Duration? optional

type Decision<X>

Carries an explicit decision and the last application value. Done(value) means the block stopped deliberately. Again(value) returned by run means the schedule was exhausted before completion. Neither form wraps the application value in an additional Result.

Variants

  • Again(X)
  • Done(X)

record Info<X>

Describes a retry that is about to wait and then execute another attempt.

Passed to onRetry only after the last outcome requests a retry and the schedule permits it. There is no notification for the initial call, success, explicit completion, or exhaustion. Reporting does not consume attempts. Durations describe scheduled sleep, not wall-clock elapsed time.

  • attempt: the just-completed attempt, starting at 1. * nextAttempt: the attempt that follows the upcoming wait. * maximumAttempts: total permitted executions, including the first. * remainingAttempts: executions remaining, including the upcoming one. * delay: actual upcoming wait, after jitter and the delay cap. * totalDelay: sleep already performed, excluding the upcoming wait. * result: the last Error or Again, including its application payload.

Fields

attempt
Integer
nextAttempt
Integer
maximumAttempts
Integer
remainingAttempts
Integer
totalDelay
Duration
result
X