> For the complete documentation index, see [llms.txt](https://docs.brainboard.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brainboard.co/automation/pipelines.md).

# Pipelines

### Description

Pipelines are the history of the execution of your workflow.

These pipelines contain both your triggered workflows and any action performed in <mark style="color:$primary;">**`one action`**</mark> tab.

![Pipeline overview](/files/AVy5vvTbnJ8oUHd56oqO)

### Pipeline information

<figure><img src="/files/W2wfTHISeNJ2egqC8EA4" alt=""><figcaption></figcaption></figure>

#### Status

There are 7 statuses of any given pipeline:

1. **Scheduled**: the pipeline is accepted by Brainboard for execution and put in the pool to be picked by a runner.
   * By default, all jobs are accepted.
2. **Pending**: the pipeline is pending to be picked by a runner to execute it.
3. **Running**: the pipeline has been picked by a runner that is currently executing its tasks.
4. **Succeeded**: the execution of the pipeline ended, and all tasks were successful.
5. **Failed**: the execution of the pipeline ended and some of the tasks failed.
   * The pipeline is considered failed, when at least one task fails.
   * When you ignore errors in tasks to not stop the pipeline, if they fail, the pipeline is considered failed even if the execution of the last task is successful.
6. **Terminated**: the pipeline has been stopped by a user.
7. **Manual**: the pipeline requires approval. It means that at least one task of the pipeline is pending approval.

<figure><img src="/files/7fKksOQZhdcZAKxw8HE2" alt=""><figcaption></figcaption></figure>

#### Unique identifier

Every pipeline has a unique identifier. It is used to store and retrieve its output.

The <mark style="color:$primary;">**`id`**</mark> displayed in this column is the last **12** characters of the **UUID** of the pipeline.

{% hint style="info" %}
The complete **UUID** is visible in the URL of the browser. You usually need it when you open a support ticket.
{% endhint %}

#### Visual stages and tasks

This is a minified graph of the pipeline.

It contains all tasks, and you can see the name and status of every task when you hover it.

#### Initiator

The avatar of the person who triggered the pipeline.

Hover this avatar to see the complete name of the person.

#### Date

Time when the pipeline was triggered.

#### Stop button

This button allows you to terminate/stop a running pipeline. It is only active when the pipeline is running.

### Run pipeline

To run the pipeline, go to the CI/CD designer and click on the button `Run pipeline`.

Refer to the [CI/CD page](/automation/ci-cd-designer.md) for more details.

### Stop pipeline

To stop the pipeline, click on the <mark style="color:red;">**`Stop pipeline`**</mark> icon located in the top right corner of the pipeline output window. This clickable icon is only active when the pipeline is running.

### Output

To open the output of any pipeline, click on it in the table of pipelines.

![Pipeline output](/files/XpOngHhXJrSA9PJd3qQQ)

#### Tasks status

Tasks have the same [status](#status) as the pipeline.