Replay
Replay re-sends a stored event to its destinations, or re-sends a single delivery. Because Webhookr stores the full payload and headers, a replay reproduces exactly what was originally received — without asking the provider to send it again.
Two granularities
| Replay | Effect |
|---|---|
| Replay event | Re-delivers the event to all currently enabled destinations on the endpoint. Updates the event's lastReplayedAt. |
| Replay delivery | Re-sends just one delivery to its destination. |
Behavior
- Each replay creates new delivery records; the originals are kept for history.
- A replay uses each destination's current configuration (URL, method, headers, timeout) — not the configuration at the time of the original event.
- Only enabled destinations are targeted.
- New deliveries resolve to
SUCCESSorFAILEDlike any other delivery. - Replay refuses an event the pipeline blocked (stopped/failed). To deliver a blocked event, use force send instead.
When to use it
- Recover events that failed while a downstream service was down.
- Re-process events after fixing a bug in a consumer.
- Push a captured production event into another environment for debugging.
How to replay
From the dashboard — see Replay — on an event or an individual delivery.