> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/dashboard-and-pipelines/pipelines/most-recent-runs/release-pipeline-run-details.md).
# Release Pipeline Run Details
**Overview**\
The Release Run Details page is a drill-down view for a specific release pipeline run. It provides a complete, stage-by-stage view of how an artifact moved through the pipeline, along with execution status, logs, and deployment reports.
This page is typically accessed from the **Release history** view when deeper investigation or validation of a specific run is required.
How to access Release Run Details
1. Navigate to Pipelines → Releases
2. From the Most recent runs view, locate the required pipeline
3. Click View details
4. From the pipeline run history, click View Details for the specific run you want to analyze\
You will be redirected to the Release Run Details page.
What you see on this page
Step 1: Pipeline execution flow\
At the top of the page, the pipeline is displayed as a visual flow starting from the artifact and progressing through each configured stage in sequence.
This view helps you quickly understand how the artifact moved across environments during this run.\
Step 2: Stage cards and execution status\
Each stage is represented as a card in the flow and displays:
* stage name
* execution status (completed, failed, in progress, pending)
* execution timestamp
This makes it easy to identify where a run succeeded, paused, or failed.
Step 3: Viewing stage logs\
For each stage, you can:
* hover over or click Logs to open the execution logs for that stage
Logs provide detailed information about deployment steps, validations, and any errors or warnings encountered during execution.\
\
Step 4: Stage-level deployment details\
Clicking on a stage opens detailed information specific to that stage, including:
* Jobs
* Deployment report
* Deployment logs
* Post Activities Report (If applicable)
\
These details are useful for troubleshooting failures, validating successful deployments, and supporting audits or reviews.\
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/dashboard-and-pipelines/pipelines/most-recent-runs/release-pipeline-run-details.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.