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

# Releases

The releases dashboard provides an overview of all running and completed releases for the apps that you have access to, and shows the current state of all releases (= the execution of a pipeline). From the dashboard you can also create a new release.&#x20;

To create a new release click on '[new release](https://docs.bluestorm.io/dashboards/releases/manage.md)' and select the app and pipeline that you want to execute.  The 'Draft' tab shows releases that have been created but have not yet been run.

To view the details of a running or completed release click on a release from the overview. To cancel a release open the release and click on 'cancel'.

Releases that are scheduled for one-time execution in the future, recuring releases (DAILY / WEEKLY), or on-commit pipelines can be viewed and cancelled from the 'Recurring' tab.

The status of scheduled or running releases is updated every 15 seconds.

{% hint style="info" %}
From the 'Completed' tab it is possible to export a list of all completed releases to an Excel spreadsheet. Note that some columns are hidden by default (E.g. Approver) and need to be unhidden if you want them to appear in the exported spreadsheet.
{% endhint %}


---

# 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.bluestorm.io/dashboards/releases.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.
