Retry on failure

import { Aside } from ‘@astrojs/starlight/components’

On Pro and Team plans, a webhook that fails to reach your deployment is automatically retried — no configuration needed.

What triggers a retry

A delivery is retried when it fails in one of these ways:

• The upstream request times out
• The upstream connection fails (target unreachable, DNS failure, etc.)
• The upstream responds with a 5xx status

A non-5xx error response (4xx) is treated as a valid delivery and is never retried — Hookman assumes your endpoint deliberately rejected the request.

Retry needs the original payload, so it only applies to projects with [payload storage](/docs/features/replay/#disabling-payload-storage) enabled. If storage is off, a failed delivery is logged but not retried.

Backoff schedule

Retries use exponential backoff, up to 3 attempts total:

Attempt	Delay after previous failure
1	Immediately
2	5 minutes
3	25 minutes

If attempt 3 also fails, Hookman stops retrying and notifies the org owner by email with a link to the failed log entry.

Where retries show up

Each retry attempt creates its own log entry in the Logs tab, with routing_method: retry and a link back to the original event — the same pattern replay uses, so you can see the full delivery history for a webhook in one place. A successful retry counts toward your monthly quota like any other delivery.

Plan availability

Plan	Automatic retry
Free	—
Pro	✓
Team	✓

There’s no dashboard toggle — retry is automatic for every project on a Pro or Team org, provided payload storage is on.