> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/playbooks/outbound-webhooks/events-and-deliveries.md).
# Events and Deliveries
## Events and Deliveries
{% hint style="info" %}
Start with [Webhooks](/playbooks/outbound-webhooks.md) for setup, destination configuration, topic selection, retention, and key behaviors.
{% endhint %}
Learn how to inspect dispatched events and troubleshoot delivery attempts after you configure one or more destinations.
### Events
The **Events** tab shows events that were dispatched to at least one configured destination.
Use this tab to audit event flow and inspect payloads. Only events that match at least one destination subscription appear here.
For topic scope and subscription setup, see [Webhooks](/playbooks/outbound-webhooks.md).
Key columns include:
* Event time
* Topic (test events are marked with a icon)
Open a row to view the full payload and metadata.
From the event detail panel, **View Deliveries** opens the **Deliveries** tab with that event pre-filtered. This will show all delivery attempts for that event.
### Deliveries
The **Deliveries** tab shows individual delivery attempts.
Each row represents one event-to-destination attempt.
Use this tab as the main debugging surface.
Key columns include:
* **Status** — `Success` or `Failed`
* **Code** — HTTP status code or provider error code
* **Attempt #** — delivery attempt number
* **Event** — opens the related event
* **Destination** — opens the destination details
Manual retries are marked with a **Manual** badge.
#### Retry a failed delivery
With the exception of test events, we will automatically attempt to retry delivery up to four times (after 30 seconds, 1 minute, 2 minutes, and 4 minutes from the previous retry, respectively). Beyond/in addition to that, you can choose to manually retry failed deliveries.
For a failed delivery, click the **Retry** icon in the actions column.
This queues a new delivery attempt for the same event and destination.
The action shows a loading spinner while the retry request is in progress.
#### Troubleshooting flow
Use this sequence when a destination does not receive an expected event:
1. Confirm the destination is enabled on [Webhooks](/playbooks/outbound-webhooks.md). Note that a destination will be automatically disabled after too many consecutive failed deliveries.
2. Confirm the topic is subscribed in the destination configuration.
3. Check **Events** to verify the event was dispatched.
4. Check **Deliveries** to inspect the response code from your configured destination and retry if needed.
5. Compare the payload with the **Topic Catalog** on [Webhooks](/playbooks/outbound-webhooks.md).
6. Check if you are using the correct [`secret`](/playbooks/outbound-webhooks.md#signature-verification) to verify the webhook signature, and using the exact, raw payload to do so.
## Metrics
The **Metrics** tab shows an at-a-glance view of the volume of events being published, and the general health of the configured destinations. You can view the following data points for up to the last 7 days:
* Aggregate event and delivery outcome statistics
* Chart showing volume of events published across topics
* Chart showing whether destinations successfully received events (retried events and events sent to multiple destinations count multiple times).
The Metrics tab, showing aggregate statistics, and volume/outcome charts.
## Related pages
* [Webhooks](/playbooks/outbound-webhooks.md)
* [Recipes](/playbooks/outbound-webhooks/webhook-recipes.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.balkan.id/playbooks/outbound-webhooks/events-and-deliveries.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.