DEADHOOK

Guides

Stop Automatic Retries

Stop future retries for one Delivery without pretending an in-flight request was aborted.

On this page

Stopping retries is a per-Delivery decision. It prevents future automatic attempts; it is not a guarantee that an already-running HTTP request is aborted.

In the dashboard

  1. Open the Delivery from Event Explorer or the Dead Letter Queue.
  2. Choose Stop retries.
  3. Enter a short reason.
  4. Confirm.

Users with Owner, Admin, or Developer permission can stop retries.

What stop means

  • No further automatic attempts will be scheduled.
  • An attempt already in flight may still complete; stopping cannot retract bytes already sent.
  • The Event and attempt history remain.
  • Stopping does not trigger a replay.
  • Stopping does not bypass Destination policy or archive state.
  • The action is recorded with the reason and actor.

A stopped Delivery is terminal for automatic work. If you later need to send it, use the explicit replay path; do not assume stop is reversible.