> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/development-cycle/overview.md).

# Run

Learn how to use the Run page on the Digibee Integration Platform to find, filter, and manage your deployed pipelines.

## **What you can do on the Run page**

Run is the phase that follows Build. On the Run page, you deploy pipelines, follow their status, and manage them in the test and production environments.

## **Select the environment**

Select the environment in the upper-left corner before you deploy or manage a pipeline:

* **Test:** Validate your pipeline without affecting live integrations.
* **Prod:** Run the pipeline in production after it has been tested.

{% hint style="info" %}
To update or fix a pipeline that is in production, make the changes in test first, then promote the pipeline to production.
{% endhint %}

## **Navigate the page**

The Run page has two tabs:

* **Pipelines:** Lists the deployed pipelines, grouped by project. Select **All projects** or a specific project in the left panel.
* **History:** Lists recent deployments across projects. See [Deployment status and history](https://docs.digibee.com/documentation/development-cycle/overview/deployment-status-and-history.md).

The page refreshes its data automatically. To change the interval or turn the refresh off, use the **Refresh data every** option below the page title.

## **Find a deployed pipeline**

Use the search bar to find deployed pipelines by name across all your projects.

You can also filter the list by:

* **Status:** Deployed, Error, Redeploy, Starting, and Deleting. See [Deployment status and history](https://docs.digibee.com/documentation/development-cycle/overview/deployment-status-and-history.md) for what each status means.
* **Triggers:** Up to five triggers.
* **Size:** Small, Medium, and Large.
* **Engine version:** The engine versions running in the current environment, newest first. Use the search box to find a specific version. Versions are shown as `x.y.z`, so different builds of the same version appear as a single option.

You can select more than one option in each filter.

Applied filters are saved in the page URL. Copy the link to share the same filtered view with your team.

## **View deployments**

You can view deployments as a list or as cards. To switch views, use the icons next to the filters.

The list view is the default. Each row shows the pipeline name and version, status, engine version, size, concurrent executions, replicas, and who deployed it and when.

Deployments are sorted by deploy date, newest first, in both views.

## **Manage a deployment**

To manage a deployed pipeline, click the three-dot menu on its row or card:

| Option                | What it does                                                                                                                                                                                            |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Promote**           | Deploys the pipeline to another environment.                                                                                                                                                            |
| **Redeploy**          | Deploys the same pipeline again with new settings.                                                                                                                                                      |
| **Rollback**          | Reverts the pipeline to the previous successfully deployed version.                                                                                                                                     |
| **Remove**            | Removes the deployment of the selected version. Other versions are not affected.                                                                                                                        |
| **Open canvas**       | Opens the pipeline in Build.                                                                                                                                                                            |
| **View executions**   | Opens the pipeline executions in Monitor.                                                                                                                                                               |
| **Open version diff** | Compares two minor versions of the deployed pipeline side by side. See [Pipeline versioning](https://docs.digibee.com/documentation/development-cycle/build-overview/pipelines/pipeline-versioning.md). |

## **Next steps**

Now that you know your way around the Run page, read [Deploy and manage pipelines](https://docs.digibee.com/documentation/development-cycle/overview/deploy-and-manage-pipelines.md) to deploy your first pipeline.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digibee.com/documentation/development-cycle/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
