> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/developer-guide/development-cycle/dashboards/completed-executions.md). # Executions Track pipeline executions, review their logs, and re-execute pipelines from the Executions tab on the Digibee Integration Platform. 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 in the Monitor area, you can track pipeline executions and their log histories, and re-execute pipelines. {% hint style="info" %} This tab was named "Completed executions" until August 2025. {% endhint %} ### **Environment selection** Select the environment you want to view from 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" %} 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 origin of the execution. When a trigger initiates the pipeline execution, this field displays the trigger name, such as `scheduler`. When executed directly from the pipeline's Execution Panel, this field displays `test`. | | **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. {% hint style="info" %} 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). {% endhint %} #### **Additional filters** In addition to the fields above, the page 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 | 1 day | Custom**: Displays executions from the last 5 minutes by default. Change the time range to 15 minutes, 1 hour, 1 day, 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 {% hint style="info" %} By default, executions are sorted by timestamp, starting with the most recent. Click the **Elapsed time** column header to sort by elapsed time instead, in ascending or descending order. This sorting applies to the full search history, not just the executions currently loaded on screen. {% endhint %} Click the **three-dot icon** to open the action menu: * **View execution**: Opens the execution in a side panel for inspection. * **Re-execute**: Opens a side panel with a payload field to re-execute the pipeline. * **Download logs**: Downloads the execution logs as a CSV file containing `timestamp`, `realm`, `pipelineKey`, `pipelineName`, `logLevel`, and `logMessage`. The default separator is a semicolon (;), but you can choose a different single character. * **Open pipeline**: Opens the pipeline where the execution ran. ### **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**: The JSON payload sent during pipeline execution. When the execution is triggered through the pipeline's Execution Panel, this payload is the `flowSpec`: a JSON object containing all the pipeline's configuration. * **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 times out, the pipeline returns an execution error message: ```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 | Truncated, with `@@DGB_TRUNCATED@@` warning | --- # 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.digibee.com/documentation/developer-guide/development-cycle/dashboards/completed-executions.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.