Skip to main content
Language reference / jitter

Meaning and placement

retry

Randomize the computed delay so tasks retrying the same upstream do not synchronize · default TRUE. Engines SHOULD use a full-jitter or equal-jitter family — the anti-thundering-herd default (spec/05-errors.md §Retry policy). In the same object: backoff_max_ms · backoff_ms · backoff_strategy · max_attempts · on_codes Schema source (use the pointer above)

In a source template

Excerpt from templates/fanout.nika, source lines 118–127. This is a fragment, not a runnable workflow.
illustration

Templates containing this field

These are literal key occurrences in the source files, not an execution or conformance claim. How to instantiate a template.

Contract and implementation

This page projects the named specification revision. Check released engine status and the validation workflow before running a file. An optional field is not evidence that every engine supports every value. Canonical identity: language:word:jitter. Spec revision: 5c40ba456c53. How documentation stays connected.