> 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/viewing-pipeline-results.md).
# Viewing Pipeline Results
{% 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
Once a pipeline is started, its progress and results can be viewed in the branch for which it was run. This article explains how to view the results of a simple pipeline.
### Operation-Specific Results
This article explains how to access the results of any pipeline operation. For operation-specific result details, see the article for that pipeline operation.
* [Pipeline Operation: Validate](/devops/pipeline/pipeline-operations/pipeline-operation-validate.md)
* [Pipeline Operation: Code Scan](/devops/pipeline/pipeline-operations/pipeline-operation-code-scan.md)
## Pipeline Results
The instructions below use a simple, single-step pipeline that was run on the Example Branch.
{% stepper %}
{% step %}
### Find Results
The pipeline results are found on the Activities tab for the branch where the pipeline was run.
1. Click **Code** from the left sidebar menu.
2. Click the branch that you ran the pipeline for.
3. Click the **Activities** tab.
{% endstep %}
{% step %}
### View Results
{% hint style="info" %}
The following instructions explain how to view a step's results from the pipeline view. Since a pipeline creates a job for each step, you can also see the results of an individual step by clicking the corresponding job in the **Jobs** table on the **Activities** tab.
{% endhint %}
1. From the **Pipelines** table, click the pipeline that you ran in the section above.
2. Each step that has run in the pipeline is marked as **Completed** (Green Checkmark Icon) or **Exception** (Orange Caution Icon).
3. Click the **Validate** step to view its results.
4. The **Logs** provide detailed messages about the step, including:
* Metadata retrieval
* Dependency checks
* Test outcomes
* Success and failure messages
{% 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/viewing-pipeline-results.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.
