Implementing Deliveries and Replay UI
Use this page to build the customer-facing diagnostics workflow for webhook failures and recovery.What to build
- Deliveries list with endpoint/status/event filters.
- Delivery detail drawer with request/response metadata.
- Replay actions for single and bulk recovery.
- Replay task monitor with cancel support.
Step 1: build deliveries list screen
endpoint_idstatusevent_name- date range in URL state (if your list supports date params elsewhere)
Step 2: add delivery detail panel
UsefetchWebhookDeliveryDetail from webhook-app-api.ts.
- Event name and delivery status.
- Attempts and timestamps.
- Response code and latency.
- Signature/debug headers if available.
Step 3: add replay actions
For targeted replay:Step 4: wire analytics and trends
Use existing hooks for summary and charting:- Failure spikes per endpoint.
- Retry volume trends.
- Success rate after replay windows.
Step 5: build safe recovery UX
- Confirm replay scope before submit.
- Show estimated replay volume before execution.
- Mark replay tasks as running/completed/failed.
- Prevent duplicate replay launches for same window.
Related docs
- React Router
useWebhookDeliveries - React Router
useWebhookAnalytics - React Router
useWebhookTimeseries - React Router
useWebhookAppSession - Webhooks Backend API Reference
Validation checklist
- Filters return expected subset of deliveries.
- Replay creates task and task status transitions correctly.
- Cancel endpoint stops running replay tasks.
- Analytics reflects post-replay recovery window.
