> For the complete documentation index, see [llms.txt](https://docs.chatlayer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chatlayer.ai/navigation/history/execution-logs.md).

# Execution logs

## Execution logs

Execution logs help you monitor and troubleshoot actions, integrations, analytics events, and voice speech-to-text failures triggered by your bot.

Use this page to inspect failures, review inputs and outputs, and verify whether expected events or voice transcriptions were handled correctly.

This page is different from **Settings** → **Audit logs** and from portal or developer app execution logs.

### Open Execution logs

Go to **History** → **Execution logs**.

The page contains four tabs:

* **Code Actions & API**
* **Integrations**
* **Tracking Events**
* **Voice**

![](/files/xF7LTSDtmjKPWXUwy8bH)

### Code Actions & API

This tab shows failed **API Action** and code action executions.

Use it to debug custom API calls and code actions that did not complete successfully.

Keep in mind:

* This tab shows errors, not every successful execution.
* You can inspect the status code, request URL, error message, timestamp, related bot dialog, bot version, request details, and response details.
* A row opens an error details drawer.
* Code actions may appear with a Chatlayer internal URL such as `chatlayer://code-actions`.
* CSV export is available for API error logs.

#### Columns

* **Timestamp**
* **Request**, including HTTP method and URL
* **Status code**
* **Error message**
* **Bot dialog**
* **Version**, such as `Draft` or `Live`

#### Filters

* **Date range**
* **Status code range**, such as `2xx`, `3xx`, `4xx`, or `5xx`
* **HTTP method**, such as `GET`, `POST`, `PUT`, `PATCH`, or `DELETE`

This tab supports CSV export for API error logs.

{% hint style="info" %}
Retention follows the bot's data retention setting for error history.
{% endhint %}

### Integrations

This tab shows executions of **App Integration** actions triggered by bot dialogs.

Unlike **Code Actions & API**, this tab can show both successful and failed executions.

Use this tab to check whether an **App Integration** action ran successfully.

You can see which action ran, which bot dialog triggered it, which account was used, and when it happened.

You can open a row to inspect the action input and output.

Failed executions show error details in the output panel.

#### Columns

* **Timestamp**
* **Status**, such as `success` or `failed`
* **Bot dialog**
* **Action**
* **Account**

#### Filters

* **Action** or app/action search
* **Date range**
* **Status**: `failed`, `success`, or any status

#### Detail drawer

Open a row to view the detail drawer.

The drawer shows the integration action name and status.

It links back to the related bot dialog when available.

It has **Input** and **Output** tabs.

* **Input** shows the JSON payload sent to the integration.
* **Output** shows the returned data for successful runs or the error object for failed runs.

Logs in this tab are scoped to the current bot version, such as `Draft` or `Live`.

### Tracking Events

This tab shows custom analytics events fired by **Track Event** blocks.

Use this tab to verify that a **Track Event** block was triggered.

Event attributes are visible in the event payload.

This helps you troubleshoot analytics instrumentation and missing event data.

#### Columns

* **Timestamp**
* **Event name**
* **Conversation ID**
* **Channel type**

#### Filters

* **Date range**
* **Event name**
* **Event properties**, such as conversation ID, channel type, channel ID, campaign ID, and language

You can expand a tracking event row to inspect the full event payload, including custom attributes.

### Voice

This tab shows speech-to-text failures from voice calls.

Use it to troubleshoot cases where Chatlayer could not initialize, connect to, stream to, or receive transcription from the configured STT provider.

Keep in mind:

* The **Voice** tab shows STT errors, not full call transcripts or recordings.
* Each row represents an STT failure during a voice call.
* You can click a row to open **Voice error details**.
* The empty state explains that STT failures during voice calls will appear here.
* Pagination shows 50 STT errors per page.

{% hint style="info" %}
Retention follows the same bot error-history retention setting.
{% endhint %}

#### Columns

* **Timestamp**
* **Provider**
* **Mode**
* **Error code**
* **Conversation**
* **Message**
* **Version**

#### Filters

* **Date range**
* **Provider**: `Microsoft` or `Google`
* **Mode**: `Sync` or `Async`
* **Error code**

#### Error codes

* `TRANSCRIBE_FAILED` — speech could not be converted to text during the call.
* `INIT_FAILED` — the STT engine could not be initialized.
* `MAX_RETRIES_REACHED` — the provider stayed unavailable after retry attempts.
* `PROVIDER_CONNECT_FAILED` — Chatlayer could not connect to the STT provider.
* `STREAM_FAILED` — the live audio stream to the provider failed or was interrupted.

#### Voice error details

Open a row to inspect the voice error details drawer.

The drawer can include:

* **Error code**
* **Provider**
* **Model**, when available
* **Mode**
* **Version**
* **Channel ID**
* **Conversation ID**
* **Timestamp**
* **Error message**
* **Details payload**, when available

Use the **Conversation ID** to find the related context in [Conversations](/navigation/history/user-messages.md).

### Troubleshooting examples

* If an **API Action** fails, open **Code Actions & API** and inspect the request URL, status code, response body, and related bot dialog.
* If an **App Integration** behaves unexpectedly, open **Integrations**, filter by action, and compare the **Input** and **Output** payloads.
* If analytics data is missing, open **Tracking Events** and check whether the expected event fired with the right attributes.
* If a voice call has transcription issues, open **Voice**, filter by provider or error code, then inspect the error details and related **Conversation ID**.

### Related pages

* [Advanced API features](/integrateandcode/custom-back-end-integrations/advanced-api-integrations.md)
* [App integrations](/integrateandcode/app-integrations.md)
* [Track events for analytics](/bot-answers/track-events-for-analytics.md)
* [Voicebot speech-to-text](/voice/phone-and-voice/voicebot-speech-to-text-fine-tuning.md)
* [Conversations](/navigation/history/user-messages.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.chatlayer.ai/navigation/history/execution-logs.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.