Executions

Track and monitor deployed integration pipelines' metrics.

This tab was named "Completed executions" until October 2025.

A execution is the record of what happened inside of the pipeline, from the moment the input passed through the trigger until it ran through the last connector in the pipeline.

In the Executions tab, you can keep track of pipeline executions and their log histories. You can also re-execute the pipelines.

Environment selection

You can select the desired environment on the upper left corner of the page. When you select an environment, the whole page refreshes to show the 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. This field uses Elasticsearch Simple Query String syntax to search within the JSON content.

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

Example:

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

Guidelines:

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

Source

The pipeline trigger.

Error code

The execution error code, based on the HTTP Status Code.

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. You can refine the results by selecting:

  • Response: Only successful executions.

  • Error: Only interrupted executions.

• Last 5 minutes: Displays executions from the last 5 minutes by default. You can change the time range to 15 minutes, 1 hour, or define a custom interval.

Execution details

To view detailed information about a pipeline execution:

1. Click the three dots (⋯) in the row of the desired execution.

2. Select View execution to open the Execution Details sidesheet.

The Execution details include:

• 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 messages – Data transmitted through the pipeline.

  • Each pipeline component (connectors, triggers, globals, etc.) receives, processes, and exports a message.

  • Only the first 50 messages are displayed, and only for executions run in the Execution panel.

• 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: The message is the data that is transmitted through the pipeline. Each component of the pipeline (connectors, triggers, globals, and so on) receives, manipulates, and exports a message. Only the first 50 pipeline messages are shown, and only for pipelines executed in the Execution panel.

If you want to analyze the execution directly in the Canvas, click Open pipeline in a new tab in the top-right corner of the sidesheet. The pipeline must have a valid pipelineId, as it is necessary to identify and navigate to the correct pipeline page.

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

Payload size	Exhibition
Smaller than 32kb	Full exhibition
Between 32kb and 320kb	Partial exhibition
Larger than 320kb	@@DGB_TRUNCATED@@ warning is shown