Skip to content
TxPipe Docs

Retry Policy

The [retries] block controls how Oura reacts when a stage fails — how many times it retries, how long it waits between attempts, and whether a persistent failure should bring the pipeline down or be skipped.

Configuration

daemon.toml
[retries]
max_retries = 20
backoff_unit_sec = 1
backoff_factor = 2
max_backoff_sec = 60
dismissible = false
  • max_retries (optional, default = 20): how many times to retry before giving up.
  • backoff_unit_sec (optional, default = 1): the base delay, in seconds, between retries.
  • backoff_factor (optional, default = 2): the multiplier applied to the delay after each attempt (exponential backoff).
  • max_backoff_sec (optional, default = 60): the longest the delay is ever allowed to grow.
  • dismissible (optional, default = false): when false, exhausting the retries tears the pipeline down. When true, the failing unit of work is dismissed and the pipeline continues.

How the backoff grows

Each retry waits backoff_unit_sec × backoff_factor^attempt, capped at max_backoff_sec. With the values above, the delays are 1s, 2s, 4s, 8s, 16s, 32s, then 60s for every attempt after that.