Retry-with-backoff policy for replaying pending offline actions.
The replay loop tracks per-action attempt counts. After maxAttempts
failed attempts the action is considered "poisoned" — it is removed from
the in-memory pending queue (so it won't block other actions) and the
optional poisonHandler is invoked. Consumers typically log the action,
surface a UI prompt, or persist it to a dead-letter store.
Defaults: 5 attempts, starting at 500ms, doubling up to 30s, with
"equal" jitter (random in [delay/2, delay]).
Retry-with-backoff policy for replaying pending offline actions.
The replay loop tracks per-action attempt counts. After
maxAttemptsfailed attempts the action is considered "poisoned" — it is removed from the in-memory pending queue (so it won't block other actions) and the optionalpoisonHandleris invoked. Consumers typically log the action, surface a UI prompt, or persist it to a dead-letter store.Defaults: 5 attempts, starting at 500ms, doubling up to 30s, with "equal" jitter (random in
[delay/2, delay]).