> ## Documentation Index
> Fetch the complete documentation index at: https://launchdarkly.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Releases page

> Read about the status of every flag release in your project in one view.

**Developer**

**Federal docs**

**EU docs**

This topic explains the Releases page, a project-level view of your flag releases. Each row shows where a flag is in its release plan, whether the release is healthy, who maintains the flag, and when the release started.

The Releases page displays the states and statuses of individual releases in one place, whether the releases were started manually or automatically.

## Prerequisites

To use the Releases page, you need:

* Access to the Release Autopilot product offering on your Developer, Foundation, or Enterprise plan.
* Flags that have a release, started from a release plan or a custom configuration.
* Permission to view releases in the project.

## Open the Releases page

To open the Releases page, navigate to your project and click **Releases** under "Feature management" in the navigation.

The Releases page is scoped to the project you are in. Use the search box and the quick filters to narrow the list.

## Read the release list

The list shows one row for each flag release that is pending, in progress, or finished. Finished releases show whether the flag is ready for code removal or archival. Expired, cancelled, and archived releases do not appear on the list.

Each row displays the flag's full release plan from start to finish, with the current environment highlighted. Flags that follow different release plans appear side by side.

Only flags that have a release appear in the list. A flag with no release does not appear, even if someone started a guarded rollout on it by hand.

Each row includes the following information:

<table>
  <thead>
    <tr>
      <th>Row element</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>Feature flag</td>
      <td>The feature flag associated with the release.</td>
    </tr>

    <tr>
      <td>Current status</td>
      <td>The release environment and the status it is in, such as Pending, In progress, Ready, Needs attention, Paused, Rolled back, or Completed.</td>
    </tr>

    <tr>
      <td>Release plan</td>
      <td>The release plan it follows, shown from the first environment to the last, followed by the cleanup steps.</td>
    </tr>

    <tr>
      <td>Maintainer</td>
      <td>The member or team that maintains the flag.</td>
    </tr>

    <tr>
      <td>Release started</td>
      <td>The date the release started.</td>
    </tr>

    <tr>
      <td>Pull request</td>
      <td>A link to the GitHub pull request that started the release. Releases that were not started from a pull request show no link.</td>
    </tr>
  </tbody>
</table>

The status in each row describes the release's current environment, which is the first environment that hasn't finished. When every environment is finished, the row shows the cleanup status instead: "Pending", "Ready", or "Completed".

## Filter the list

Use the search box to find a flag by name or key. Use the **All releases**, **Regressions**, or **Ready for cleanup** quick filters to narrow the list. The **Regressions** filter excludes rolled-back releases.

To see only the flags that a member or team maintains, click the maintainer's name in the relevant row.

## View release details

To read about the details of a release, click the flag name in the "Feature flag" column. This opens the flag's release overview, where you can read about the pull request that started the release, the rollout steps for each environment, and the cleanup steps.

To preview a release without leaving the Releases page, hover over the status in the "Current status" column, or an environment in the "Release plan" column.

The Releases page is read-only. To roll back a release, dismiss a regression alert, or stop monitoring a guarded rollout, open the flag's **Targeting** or **Monitoring** tab. To pause or resume auto-release, go to the flag's **Release** tab and click **Pause auto-release** or **Resume auto-release**. To learn more, read [How auto-release works](https://launchdarkly.com/docs/home/release-autopilot/autorelease.md#how-auto-release-works).

## Get release data programmatically

The Releases page shows flag releases. You can get the status of a flag's release in each environment through the [Environment releases REST API](https://launchdarkly.com/docs/api/environment-releases), which is in public beta. Use it to list and get a flag's current and past releases in an environment, and to start or stop a release in an environment. The API returns releases that ended within the last 90 days.

Requests require the `LD-API-Version: beta` header. The LaunchDarkly CLI includes matching commands in the `environment-releases-beta` group: `list`, `get`, `start`, and `stop`.

Run `ldcli environment-releases-beta --help` to see them. With the API or the CLI, an agent or integration can check whether a release in an environment finished or is stuck without opening the UI.

A release in an environment is made up of phases, and each phase is made up of rollout steps. Each environment in a release plan has one of the following statuses.

The API values don't always match the labels shown for environments on the Releases page. The following table shows the label each value appears as for the release environment:

<table>
  <thead>
    <tr>
      <th>API status value</th>
      <th>Releases environment label</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>`pending`</td>
      <td>Pending</td>
      <td>The release or phase has not started.</td>
    </tr>

    <tr>
      <td>`in_progress`</td>
      <td>In progress</td>
      <td>The release or phase is progressing and does not need action.</td>
    </tr>

    <tr>
      <td>`waiting`</td>
      <td>Regression detected or Next phase ready</td>
      <td>The rollout is partially complete, paused, and waiting for you to take action. A `waiting` environment shows as "Needs attention" with the reason "Regression detected," or as "Needs attention" with the reason "Next phase ready".</td>
    </tr>

    <tr>
      <td>`completed`</td>
      <td>Completed</td>
      <td>The release or phase reached the target variation.</td>
    </tr>

    <tr>
      <td>`reverted`</td>
      <td>Rolled back</td>
      <td>The release or phase returned to the original variation.</td>
    </tr>
  </tbody>
</table>

The Releases page also uses two labels that don't come from an API status. "Ready" means the flag is ready for code removal or archival. "Paused" means auto-release is paused and won't advance until someone resumes it.

An environment or phase with the `waiting`, `completed`, or `reverted` status can also have one of the following `statusReason` values:

<table>
  <thead>
    <tr>
      <th>Status reason value</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>`waiting_regression_detected`</td>
      <td>LaunchDarkly detected a regression in a monitored metric and paused the rollout until you take action.</td>
    </tr>

    <tr>
      <td>`waiting_phase_ended`</td>
      <td>A phase of a multi-phase release that advances manually ended, and you must advance the release to the next phase. This value appears only on the release in an environment, never on a phase.</td>
    </tr>

    <tr>
      <td>`completed_automatic`</td>
      <td>The release or phase reached the target variation automatically.</td>
    </tr>

    <tr>
      <td>`completed_manual`</td>
      <td>A member completed the release or phase manually.</td>
    </tr>

    <tr>
      <td>`reverted_regression_detected`</td>
      <td>LaunchDarkly detected a regression and rolled back the release.</td>
    </tr>

    <tr>
      <td>`reverted_manual`</td>
      <td>A member rolled back the release manually.</td>
    </tr>

    <tr>
      <td>`reverted_discarded`</td>
      <td>The phase ended without a regression or a manual rollback. A running phase is discarded when the flag changes during the phase, for example when someone turns off, archives, or deletes the flag. A pending phase is discarded when the release ends before the phase starts. The release in an environment has this value only when the last phase that started was discarded.</td>
    </tr>

    <tr>
      <td>`reverted_insufficient_data`</td>
      <td>LaunchDarkly rolled back the release or phase because there was not enough data to evaluate it.</td>
    </tr>
  </tbody>
</table>
