Find executions

Tens of thousands of pipelines might execute in a production environment in a short time period. Use the following controls on the Pipeline executions page to find a pipeline of interest:

  • For the Execution history table, select the smallest time period possible to reduce the number of executions in the list.
  • Click the arrow on a sortable column, , to sort ascending or descending.
  • For the Execution history table, use the Filter presets (Errors, Stopped, Completed) or click the funnel icon on a specific column to filter it. You can filter the Type, Status, and Project.
  • Click Table configuration and filters to open the Table configuration and filters dialog to hide or show columns, set filters, and rearrange columns.

Filters apply to searches and the execution list for the current session. To remind you that filters are active, the filter icon fills, , and the Table configuration and filters control is marked with a purple dot .

The following sections describe how to find and filter the required pipelines:

Clear filters

To clear filters, do any of the following:
  • Click an active preset filter to clear it.
  • Clear a column filter by clicking its filter icon, . For the multi-select Status and Project column filters, clear values individually or by clicking the Select All checkbox twice. For the Type column filter, click All.
  • In the table header, click Clear all filters.
  • Clear specific filters or all filters from the Table configuration and filters control, . Unset specific filters or click Clear all filters, and click Apply.

Search failing or failed executions

Search failed executions in one of the following ways:

  • Click the Errors filter preset. This selects all executions with a status of failed or completed with errors.
  • From the Status column:
    1. Click the filter icon, .
    2. Select Failing (available in the Running pipelines table) or Failed (available in the Execution history table).
  • From the Table configuration and filters control, :
    1. Scroll to the Status column.
    2. Select Failing (available in the Running pipelines table) or Failed (available in the Execution history table).
    3. Click Apply.

Use multiple filters

You can apply multiple filters in both tables by clicking on individual columns, or from the Table configuration and filters dialog. In the Execution history table, you can also use Filter presets (Errors, Stopped, Completed) as a starting point.

  1. On the right side of the table header, click the Table configuration and filters control, .
  2. Select the appropriate filter values.
  3. Click Apply.

Search by invocation type

You can filter by one invocation type at a time. Find an execution by invocation type in one of the following ways:

  • From the Type column:
    1. Click the filter icon, .
    2. Select the invocation type.

  • From the Table configuration and filters control, :
    1. Scroll to the Type column.
    2. Select an invocation type.
    3. Click Apply.
The Type column filter includes the following options:
Filter by type

Search for parent and child pipeline executions

With the Nested filter selected for the Type column, only parent and child executions display. You can search by name or other criteria to narrow the list of executions. Search results show parent and child pipelines together.

Click a parent to open the details panel, which contains the Children tab:


Pipeline details panel showing the Snap statistics tab for a parent pipeline.

The Children tab lists the parent's immediate children.


Children tab in the pipeline details panel, showing a flat list of immediate child executions.

You can:

  • Use the Pipeline filter to search by name.
  • Use the Status filter to filter by status.
  • Click a child pipeline name to open its details panel. The header shows the full hierarchy as a series of clickable links for navigation. The Parent pipeline path field in the header opens the parent pipeline in Designer.
    Pipeline details panel header showing the hierarchy as clickable navigation links.

  • If a child pipeline has its own children, click the child execution row to open its details and view its children on the Children tab. You can continue navigating down through the hierarchy one level at a time.

Search for pipelines in deep hierarchies

When you search in the nested view, the table flattens hierarchies of more than two levels to reduce the number of displayed rows. The table shows the top-level parent, a placeholder row for hidden intermediate levels, and child pipelines that match the search term.


Expand hidden hierarchy.

To view the hidden levels, click the Expand hidden hierarchy (N levels) row. The table displays all intermediate levels between the parent and matched pipelines.

Note: Hierarchy flattening applies only during active searches. When you clear or modify the search, the table returns to the default collapsed view.

The following scenarios illustrate how the table displays search results at different hierarchy depths:

Scenario 1: Matches in level one or two

When a search matches a pipeline one or two levels below its parent, the table displays the complete hierarchy. For example, a search that matches a child pipeline shows both the parent and the matched child with the standard hierarchical indentation.

Parent pipeline
  └─ Child pipeline (matched)

Scenario 2: Matches in level three or greater

When a search matches a pipeline three or more levels below its parent, the table displays:

  • The top-level parent pipeline
  • A placeholder row labeled Expand hidden hierarchy (N levels)
  • The matched pipelines

For example, if a matched child pipeline is five levels deep, the table shows the top-level parent, the placeholder row indicating three hidden levels, and the matched pipeline.

Top-level parent pipeline
  └─ Expand hidden hierarchy (3 levels) ▼
     └─ Child pipeline (matched)

Scenario 3: Multiple matches under a common parent

When pipelines at different levels match the search and share a common parent, the table groups them under a single placeholder row. Individual hierarchical relationships between the matched pipelines aren't displayed. For example, Pipeline A and Pipeline B have different parent pipelines between them and the common parent, but these intermediate levels are hidden by default.

Common parent pipeline
  └─ Expand hidden hierarchy ▼
     ├─ Pipeline A (matched)
     ├─ Pipeline B (matched)
     └─ Pipeline C (matched)

Search by runtime ID (RUUID)

Paste a runtime ID directly into the Search box or the Filter dialog to find a specific execution. To navigate a deep hierarchy of parent-child executions, use the Children tab in the pipeline details panel as described in Navigate child executions.