Executions
Track and monitor deployed pipeline metrics.
This tab was named "Completed executions" until August 2025.
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.
You can also run the search using Ctrl+Enter (Windows) or Cmd+Enter (macOS).
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.
Filtering by pipeline name
The Name filter is an autocomplete that lists available pipelines. The list supports infinite scroll and loads more results as you navigate down.
Exact
Click an option in the dropdown list.
Filters results for that specific pipeline.
Approximate
Type a term and press Enter.
Filters results by similarity.
Searching by payload
To ensure accurate results, escape characters when searching for exact key-value pairs.
Example:
Follow these guidelines when writing payload queries:
Escape quotes (
\") to match exact key-value pairs in the JSON payload.Use the plus operator (
+) to apply a logical AND between conditions.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.
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 | 1 day | 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:
Payload exhibition limits
In some cases, the Digibee Integration Platform presents truncated payloads according to the following criteria:
Smaller than 32 KB
Full exhibition
Between 32 KB and 320 KB
Partial exhibition
Larger than 320 KB
@@DGB_TRUNCATED@@ warning is shown
Last updated
Was this helpful?