> For the complete documentation index, see [llms.txt](https://docs.pipekit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pipekit.io/using-pipekit/runs/filters.md).

# Filtering Runs

Narrow the Runs list to the runs you care about, and save a set of filters to reuse.

The Runs list starts unfiltered. It shows every run you have access to, from everyone in your organization, until you narrow it.

## Filtering the list

Click `Filters` above the Runs list to open the filter panel, which is titled `Filter by`. The button shows a count of how many filters are currently active.

You can filter on:

| Field            | Narrows the list to                                          |
| ---------------- | ------------------------------------------------------------ |
| `Source`         | Runs started by a particular trigger source                  |
| `Labels`         | Runs carrying the labels you choose                          |
| `Cluster`        | Runs that ran on one of your registered Clusters             |
| `Status`         | Runs in the states you choose, such as `Running` or `Failed` |
| `Started after`  | Runs that started on or after a date                         |
| `Started before` | Runs that started on or before a date                        |
| `User`           | Runs started by the users you choose                         |
| `Namespace`      | Runs in a particular Kubernetes namespace                    |
| `SHA/Branch/Tag` | Runs built from a specific commit, branch, or tag            |
| `Workflow Name`  | Runs of a particular Argo `Workflow`                         |

An unset field shows an `All ...` placeholder, so an untouched panel filters nothing out.

Filters combine. To review yesterday's failures on one cluster, set `Status` to `Failed`, `Cluster` to that cluster, and `Started after` to yesterday's date.

Your current filter values stay applied as you move around and come back to the Runs tab. To go back to seeing everything, click `Reset` at the bottom of the panel.

## Saving a filter

If you use a combination often, save it and reapply it by name instead of rebuilding it each time.

Set the filters you want, then click `Save Current Filters` at the bottom of the panel and give it a `Filter name`. The saved filter then appears in the dropdown above the Runs list.

Select a saved filter to apply its values to the list. Select it again to deselect it, which clears those values and shows every run again. When you delete a saved filter, Pipekit asks you to confirm under `Delete Saved Filter`. If that filter was active, its values are cleared as well, so the list does not stay filtered by something that no longer exists.

You can keep up to 20 saved filters.

## Sharing a filtered view

Every filter you apply is written to the page URL, whether you set it by hand or by selecting a saved filter. Copying the URL from the address bar therefore gives someone else the same filtered list.

A link made from a saved filter also carries that filter's identifier. Saved filters live in your own browser, so Pipekit ignores that identifier for anyone else. They see the same runs, but no saved filter is selected in their dropdown.

## The `My Runs` filter

The first time you open the Runs tab in a browser, Pipekit creates a saved filter called `My Runs` that scopes the list to runs you started. It keeps your own runs one click away without hiding your colleagues' runs by default.

`My Runs` is an ordinary saved filter once created. You can rename it, change what it filters on, or delete it. Deleting it is permanent in that browser. Pipekit does not recreate it on your next visit.

{% hint style="info" %}
Filters and saved filters are stored in your browser, per user account. They do not follow you to another browser or device, and they are not shared with the rest of your organization. Opening Pipekit in a new browser gives you a fresh, unfiltered Runs list and a new `My Runs` filter.
{% endhint %}