# Executions

{% hint style="info" %}
This tab was named "Completed executions" until August 2025.
{% endhint %}

An execution is the record of what happened inside a pipeline, from the moment the input passed through the trigger until it ran through the last connector. In the Executions tab, you can keep track of pipeline executions and their log histories, and re-execute pipelines.

### Environment selection

Select the desired environment on the upper left corner of the page. When you select an environment, the page refreshes to show data related to the pipelines in that environment. Each environment is color-coded to make identification easier.

### Search fields

Use the fields below to filter pipeline executions. The results list displays executions that match the selected criteria.

{% hint style="info" icon="lightbulb-exclamation-on" %}
You can also run the search using **Ctrl+Enter** (Windows) or **Cmd+Enter** (macOS).
{% endhint %}

| Field             | Description                                                                                                                   |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| **Pipeline**      | The pipeline name.                                                                                                            |
| **Version**       | The pipeline version number.                                                                                                  |
| **Execution key** | The unique identifier of a pipeline execution.                                                                                |
| **Payload**       | The pipeline input or output in JSON format. Uses Elasticsearch Simple Query String syntax to search within the JSON content. |
| **Source**        | The pipeline trigger.                                                                                                         |
| **Error code**    | The execution error code, based on the HTTP Status Code.                                                                      |

#### Searching by payload

To ensure accurate results, escape characters when searching for exact key-value pairs.

**Example:**

```
\"channelId\": \"63\" + \"method\": \"POST\"
```

Follow these guidelines when writing payload queries:

1. Escape quotes (`\"`) to match exact key-value pairs in the JSON payload.
2. Use the plus operator (`+`) to apply a logical AND between conditions.
3. Escape JSON content to prevent special characters such as `:` from being interpreted as query operators.

Following these rules helps you reliably filter executions based on payload content. Learn more about [Simple Query String syntax](https://www.elastic.co/docs/reference/query-languages/query-dsl/query-dsl-simple-query-string-query#simple-query-string-syntax).

#### Additional filters

In addition to the fields above, the interface provides always-visible quick filters:

* **Any message**: Shows executions of all message types by default. Refine results by selecting:
  * **Response:** Only successful executions.
  * **Error:** Only interrupted executions.
* **Last 5 minutes | 15 minutes | 1 hour | Custom**: Displays executions from the last 5 minutes by default. Change the time range to 15 minutes, 1 hour, or define a custom interval.

### Executions table

The executions table shows execution data for the selected pipelines in the selected period.\
It includes:

* Timestamp
* Message type
* Elapsed time
* Source
* Pipeline name
* Execution key

Action menu (Available by clicking the **three-dot icon**):

* View execution
* Re-execute
* Download logs
* Open pipeline

### Execution details

To view detailed information about a pipeline execution, click the three-dot icon on the selected execution. The execution details panel includes the following:

* **Pipeline execution key** — Unique identifier of the pipeline execution.
* **Request message** — JSON payload sent by the pipeline trigger.
* **Response message** — JSON output returned by the pipeline.
* **Execution logs** — Logs generated during the execution. Click the eye icon to view a log message. You can copy the message or format the JSON directly in this view.
* **Execution messages** — Data transmitted through the pipeline. Each component (connectors, triggers, globals, and so on) receives, manipulates, and exports a message.

#### Timeout errors

If the request fails due to a timeout, you will receive a message about the execution error:

```json
{
  "statusCode": 504,
  "message": "The message expired on queue and was not processed by the pipeline."
}
```

#### Payload exhibition limits

In some cases, the Digibee Integration Platform presents truncated payloads according to the following criteria:

| Payload size             | Exhibition                           |
| ------------------------ | ------------------------------------ |
| Smaller than 32 KB       | Full exhibition                      |
| Between 32 KB and 320 KB | Partial exhibition                   |
| Larger than 320 KB       | `@@DGB_TRUNCATED@@` warning is shown |


---

# Agent Instructions: 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:

```
GET https://docs.digibee.com/documentation/developer-guide/development-cycle/dashboards/completed-executions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.