> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/data-and-integrations/webhooks/webhook-execution-log.md).

# Webhook Execution Log

Each webhook execution is logged in the system for reference and debugging.

To view the execution log for any webhook, go to its 'History' tab - there you'll get a top-level list view of the most recent execution along with details of when the execution happened and whether it was successful.  You can drill into any execution for more details by clicking 'View'.

### Successul Executions

For executions which were successful, you'll simply see the server result (200).

### Unsuccessful Executions

In the case of failed executions, the system logs more information for debugging purposes:

* Result: will either be a non-200 result in the case of server errors, or 0 in the case that the server was not reached
* Headers: the headers that were sent as part of the request
* Request Body: a copy of the JSON payload that was sent
* Response Body: a copy of the JSON response from the server
* Hard Error: a hard error means the server was not even reached
* Error Message/Error: in the case of a hard error, error messages are logged


---

# 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.pakk.io/data-and-integrations/webhooks/webhook-execution-log.md?ask=<question>&goal=<endgoal>
```

`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.