Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.maia.ai/llms.txt

Use this file to discover all available pages before exploring further.

Your activity is the pipeline run history feature that lists all pipelines, including those executed manually, scheduled, or via API.

Accessing the dashboard

There are two ways you can access the pipeline run history dashboard:
  1. Log in to .
  2. In the left navigation, click the Activity icon. Then, select Pipeline runs from the menu.
Or:
  1. Log in to .
  2. The Home tab will be open. Click the View pipeline runs tile.
Either of these methods will open Your activity with the tab displayed.

Pipeline run history

The 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.
  • 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 , pipeline run information is organized into the columns described below.

Pipeline run table columns

ColumnDescription
PipelineThe 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.
ProjectThe project that contains the pipeline.
StatusThe 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.
EnvironmentThe environment where the pipeline was run.
Artifact versionThe 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 byThe user or process that triggered the pipeline run, such as a schedule, a manual run by a user, or an API call.
Started atThe date and time when the pipeline run started.
Ended atThe date and time when the pipeline run finished.
DurationThe 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.

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

Saved views

Save your applied filters as a named view so the Pipeline runs page opens in the state you want, without re-applying filters each visit. This is useful if you regularly return to the page with the same filters in place—for example, a production support lead monitoring failed runs in the last 24 hours. A saved view stores any combination of:
  • Project
  • Status
  • Environment
  • Time range
You can save multiple views, switch between them from the Saved filters drop-down in the top-right corner of the Your activity page, and mark one view as your default to load automatically when you open the page.

Save a view

  1. On the Your activity page, apply the filters you want to save.
  2. Click the Saved filters drop-down in the top-right corner.
  3. Click + Save current filters….
  4. Enter a name for the view, for example, “Prod monitoring”.
  5. (Optional) Select Set as default view.
  6. Save the view.
The new view appears in the Saved filters drop-down. To delete a view, open the Saved filters drop-down, and click the bin icon next to the view.

Switch between saved views

  1. Click the Saved filters drop-down.
  2. Select a named view from the list.
The page updates to show pipeline runs matching the saved filters.

Set a default view

A default view loads automatically each time you open the Your activity page.
  1. Click the Saved filters drop-down.
  2. Click the star next to the view you want to set as the default.
When the star is filled, that view is your default. Click the star again to remove the default.

Cancel pipeline runs

To cancel a pipeline that is running:
  1. In the left navigation, click the Activity icon. Then, select Pipeline runs from the menu.
  2. Ensure that the tab is open.
  3. Locate your running pipeline and click the three dots .
  4. 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 .