> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/devops/pipeline/pipeline-actions/running-a-pipeline.md).
# Running a Pipeline
{% hint style="warning" %}
#### Written for the Old UI
This article was written for the old UI. The instructions are still usable, but the screenshots are outdated. In some cases, items referenced in the instructions have moved or changed. If you cannot find an item, see the [Where Did It Go](/devops/new-ui-ux-transition/where-did-it-go.md) article.
{% endhint %}
##  Overview
Starting a pipeline begins the execution of its defined steps. This article guides you through running the current pipeline directly from the pipeline editor. Alternatively, you can also run a pipeline from a branch or the Pipeline page. Regardless of the method you choose, the instructions are generally similar.
## Run Pipeline
{% stepper %}
{% step %}
### Open Pipeline
1. Click **Pipelines** from the left sidebar menu.
2. Click the **Pipeline** to run.
{% endstep %}
{% step %}
### Run Pipeline
1. Click **Run pipeline**.
2. Click the **Select** **branch** dropdown menu.
3. Select the branch to run the pipeline for.
4. Click **Run**.
5. After clicking **Run**, the pipeline job starts, and a **Pipeline ran successfully** message is displayed.
{% hint style="warning" %}
The **Pipeline ran successfully** message only means that the pipeline job was successfully started. This message does not indicate that the pipeline completed all of its operations successfully. To view the pipeline results, check the branch's activity.
{% endhint %}
{% endstep %}
{% step %}
### Find Results
Viewing a pipeline's progress and results is done from the branch on which the pipeline was run. See the following article for instructions on viewing a pipeline's results.
* [Viewing Pipeline Results](/devops/pipeline/pipeline-actions/viewing-pipeline-results.md)
{% endstep %}
{% endstepper %}
---
# 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.flosum.com/devops/pipeline/pipeline-actions/running-a-pipeline.md?ask=&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.
