> ## Documentation Index > Fetch the complete documentation index at: https://repost.sh/docs/llms.txt > Use this file to discover all available pages before exploring further. # Inspect Webhook Event History and Deliveries in Repost > Use Repost event history to trace every webhook from provider to destination, inspect raw payloads, and identify delivery failures fast. Event history is the operational record for every webhook that passes through Repost. It captures the inbound request, the response Repost returned to the sender, every delivery attempt created for your forwarders, and all the payload data you need to debug or replay an event. Whether you are confirming a provider called your endpoint or diagnosing why a delivery failed, history is the place to start. ## Two levels of history Repost gives you two complementary views. Start at the bucket when you need to know what arrived. Open forwarder history when you want to trace delivery behavior for a specific destination. Shows each inbound webhook received by a bucket. Use it to confirm that a provider called Repost, inspect the raw request and the response Repost gave back, open a deep link to a specific event, and see which forwarders it was dispatched to. Shows delivery attempts for one forwarder. Use it to inspect target URLs, destination response codes, attempt counts, transform timing, retry state, and which events are candidates for replay. ## Follow one event end to end Select any row in bucket or forwarder history to open the detail drawer. The URL updates with the selected identifier so you can share the exact view with a teammate. Search by method, path, status, payload field, or time range. An empty query shows every event in the current history window. Click a row to open the detail drawer. The URL is updated with the selected event or forward identifier, making the view shareable. Bucket event detail surfaces **Overview**, **Request**, **Response**, and **Forwards** tabs. Forwarder detail surfaces **Overview**, **Request**, **Response**, **Event**, and **Attempts** tabs. Copy links or JSON values, add scalar values back into the search query, generate TypeScript types from a bucket request body, use a forward as function test input, or start a replay directly from the drawer. ## Live tail and historical windows History opens in live mode by default. If you arrive through a deep link or select an explicit time range, Repost switches to historical mode and keeps the list pinned to that window. New rows stream in as traffic arrives. If you scroll away from the latest row, an indicator counts new arrivals. If rows were not shown live, the not-shown counter reloads the latest stored history when you click it. The date picker and timeline histogram let you select a bounded window. Bucket history also accepts typed `received_at` clauses in the query editor. The earliest selectable time is governed by your plan's retention period. Opening a shared event or forward URL anchors the table around that specific row instead of immediately following the latest traffic. Switching back to live mode clears the selected historical window so both the latest event stream and the history list point at now. ## Use the table as a working surface The history table is built for repeated investigation. You can customise its layout, read traffic patterns from the timeline, and share your exact view without reapplying filters. Show, hide, resize, and reorder columns. Add custom columns sourced from JSON paths when a specific payload field deserves a permanent place in your table view. The timeline above the table summarises traffic over the visible time frame. Bucket history groups events by HTTP status class; forwarder history groups delivery attempts by delivery status. Each page loads up to 500 rows. When live tail is off and the table is not at the latest traffic, the page checks for newer rows every 30 seconds and lets you jump forward. The selected event and forward identifiers are stored in the URL alongside the query. Copy that URL when escalating a delivery issue to a teammate. ## Replay from history Replay uses the history view as its selection surface. You can redeliver a single event from the detail drawer or replay a filtered set of forwards from forwarder history — all without contacting the original provider. From bucket event history, choose one or more active forwarders. From forwarder history, replay the event to the same forwarder. Repost creates a separate replay job for each selected forwarder. From forwarder history, select specific rows or use **Replay All** against the current query and time window. Repost deduplicates the set by event ID before the job starts. Replay sends real traffic to your destinations. Use a tight query and time window before replaying all matching history. ## Failed deliveries Queued bucket forwarders expose a failed-deliveries view for delivery attempts that exhausted all automatic retries and need operator action. Inspect failed event details, prior attempts, destination response codes and bodies, and choose to replay or archive each item. Tune timeout, retry delays, backoff, rate limits, and circuit breaker settings to reduce future failures. ## Search history The same query editor powers both bucket and forwarder history. You write field clauses, range filters, and boolean operators once and apply them across all your history views. Field names, value syntax, boolean operators, range expressions, JSON path queries, and common example queries. Hover any scalar JSON value in an event or forward detail drawer to include it in the query, exclude it, or copy the value to your clipboard.