Skip to main content

Replay

Replay re-sends a stored event to its destinations without the original provider having to send it again. Use it to recover from outages, retry failed deliveries, or push a captured event into a service after a fix.

Because Webhookr stores the full payload and headers of every event, a replay sends exactly what was originally received.

Replay an entire event​

From an event's detail page (/dashboard/events/<endpointId>/<eventId>), choose Replay. Webhookr re-delivers the event to all currently enabled destinations on the endpoint, creating new delivery attempts.

The event's last replayed at timestamp is updated so you can tell when it was last reprocessed.

note

A screenshot of the replay action on an event will be added here.

Replay a single delivery​

From a delivery's detail page (/dashboard/events/<endpointId>/<eventId>/deliveries/<deliveryId>), choose Replay to re-send just that one delivery to its destination. This is the targeted option when only one destination failed and you don't want to re-send to the others.

What to expect​

  • Replays create new delivery attempts; the original deliveries are preserved for history.
  • A replay uses each destination's current configuration (URL, method, headers, timeout) and only targets enabled destinations.
  • The outcome appears as a new delivery with its own SUCCESS / FAILED status, response status, body, and duration.
tip

If a destination was disabled or reconfigured since the original event, the replay reflects the current setup — not the configuration at the time of the original delivery.

Next​