Pipeline Observability dashboard🔗

The Pipeline Observability dashboard is a feature of the Data Productivity Cloud that lists all Data Productivity Cloud pipelines, including those executed manually, scheduled, or via API.

Accessing the dashboard🔗

There are two ways you can access the Pipeline Observability dashboard:

Log in to the Data Productivity Cloud.
In the left navigation, click the Activity icon . Then, select Pipeline runs from the menu.

Or:

Log in to the Data Productivity Cloud.
The Home tab will be open. Click the View pipeline runs tile.

Either of these methods will open Your activity with the Data Productivity Cloud tab displayed.

Pipeline run history🔗

The Data Productivity Cloud tab provides a comprehensive view of historical pipeline run details. It includes pipelines run manually, triggered by a schedule, or invoked through the API.

You can:

View pipeline run history for the past 12 months.
Search by pipeline name or execution ID.
Filter results by time frame.
Re-run eligible pipelines.

Note

Pipeline run records are kept for one year; pipeline run details are retained for 90 days.
Some runs may display anomaly warnings if execution time deviates from recent trends. To learn how Maia can help identify anomalies, read Anomaly detection.

For the Data Productivity Cloud, pipeline run information is organized into the columns described below.

Pipeline run table columns🔗

Column	Description
Pipeline	The name of the pipeline that was run. Click the pipeline name to open a separate page that shows pipeline metadata, including pipeline details, individual component details, full folder paths (if available), and any error logs.
Project	The project that contains the pipeline.
Status	The current state of the pipeline run. While the pipeline is running, the status is Running. When the run completes, the status can be Success, Failed, Cancelled, or Skipped.
Environment	The environment where the pipeline was run.
Artifact version	The version of the pipeline definition that was used for the run. This helps you identify exactly which version executed when troubleshooting or reviewing changes.
Triggered by	The user or process that triggered the pipeline run, such as a schedule, a manual run by a user, or an API call.
Started at	The date and time when the pipeline run started.
Ended at	The date and time when the pipeline run finished.
Duration	The total time taken for the pipeline run to complete.

Click the link to the right of your pipeline to open your project.

Skipped pipeline runs🔗

A pipeline run is marked as Skipped when a scheduled execution is prevented from running due to concurrency restrictions. Skipped runs are recorded in the run history, but no pipeline components are executed.

This occurs when:

A schedule has Allow concurrent schedule runs set to false, and
A new execution request is triggered for that schedule while a previous root pipeline execution (with the same schedule ID) is still in progress.

Re-run pipelines🔗

You can re-run pipelines directly from the pipeline run history dashboard. This allows you to safely re-execute pipelines without opening Designer, ensuring the original published pipeline definition is used.

In the left navigation, click the Activity icon . Then, select Pipeline runs from the menu. This opens the Your activity page, which displays the pipeline run history.
Locate and click the pipeline run you want to re-run.
In the Pipeline run details, click Re-run pipeline.

This action:

Starts a new pipeline execution.
Creates a new entry in the Your activity (Pipeline run history) dashboard.
Re-runs the pipeline using the same published Artifact version as the original execution.

Note

The Re-run pipeline button is available only for eligible runs (for example, scheduled or API-triggered runs) and only for users with permission to run published pipelines.

If you have a Viewer role, the option is disabled (grayed out). For more information about roles and permissions, read Project roles and Environment roles.

Re-run a specific pipeline step🔗

Within the pipeline run details view, there are two icons to the right of each pipeline step. Each icon represents a different re-run behavior:

Run from step: Runs the selected step and all downstream steps.
Run only step: Runs only the selected step, without executing any upstream or downstream steps.

Both options start a new pipeline execution and appear as a new entry in the pipeline run history.

Warning

Re-running a pipeline from a specific step does not restore variable values, transaction states, or upstream execution context.

Step-level re-runs should be used only when you are confident that downstream steps can safely run in isolation.

Filter pipeline runs🔗

Filter your pipeline runs by clicking the Filter icon next to the Project, Status, and Environment headings at the top of the Your activity page. For example, you can filter by project, by the environment within a specific project, or by the status of a pipeline run. By default, the page displays all pipeline runs across your account, regardless of the project.

You can apply multiple filters at the same time to narrow the list of displayed pipeline runs.

Filtering options🔗

Status: Use the Status filter to view pipeline runs by outcome. The available statuses are Success, Failed, Cancelled, and Skipped, and are displayed as checkboxes. Click one or more checkboxes to filter results. The page updates automatically to display pipeline runs that match your selections. Click Clear to remove all filters and return to the full list of pipeline runs.
Project: Use the Project filter to view pipeline runs for a specific project. You can filter by multiple projects. The page will update to show only the pipeline runs associated with the selected project.
Environment: After selecting a project, you can further filter by Environment to view pipeline runs executed in a specific environment within that project. You can filter by multiple environments. The page will update to reflect your selection.

Search pipeline runs🔗

Use the search bar at the top of the page to find specific pipeline runs.

You can search by:

Pipeline name
Execution ID

Cancel pipeline runs🔗

To cancel a pipeline that is running:

In the left navigation, click the Activity icon . Then, select Pipeline runs from the menu.
Ensure that the Data Productivity Cloud tab is open.
Locate your running pipeline and click the three dots ... .
Click Cancel run or Force cancel.
Cancel run: This is a "soft" cancellation, and will allow the current task to complete. After that, no other pipeline tasks will run.
Force cancel: This is a "hard" cancellation, and will interrupt and terminate the current pipeline task, set the pipeline status to "Stopped", and prevent the pipeline from running any more tasks.

You can also cancel pipeline runs within Designer.