---
title: Flag statuses in Feature Experimentation
slug: feature-experimentation/docs/flag-statuses-in-feature-experimentation
docTags: 
createdAt: 2026-08-05T20:40:00.000Z
---

:::hint{type="success"}
**Products**

- Optimizely Feature Experimentation

The availability of features may depend on your plan type. Reach out to your Customer Success Manager if you have any questions.
:::

Flag statuses show where each flag is in its lifecycle: draft, testing, live, paused, stale, or archived. Feature Experimentation calculates all statuses automatically (using the ruleset state, rule state, environment type, and time-based activity signals), except archived, which you set manually. Use flag statuses to identify which flags need attention and prevent forgotten or unused flags from accumulating.

:::hint{type="success"}
**Beta**

This feature is currently in beta. Contact your Customer Success Manager or [sign up for the beta on Optimizely.com](https://www.optimizely.com/beta?_gl=1*1nsunuu*_ga*OTc4NDgwMjkzLjE3MTc0MjI0NDY.*_ga_C7SLJ6HMJ5*MTcxNzUxNTc3Mi41LjEuMTcxNzUxNTg0My41Ni4wLjA.*_gcl_au*MTY1NzI3NzI3My4xNzE2OTkzNTY2).
:::

## Flags dashboard

Go to **Flags**.

![Screenshot of the Flags dashboard showing flag status indicators for each flag](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/GDanp5W34Mm_soXiRtHd5-20260720-145743.png)

The **Flags** dashboard shows the status and rules for each flag in your Feature Experimentation project. To learn how to create a flag, see [Manage flags](docId\:j7bgkTxrI8VN_z2dOZu1R).

## Flag statuses

A flag can take on one of the following statuses:

- [Draft](docId\:fnh4OuAh1KEiMctPuUoep)
- [Testing](docId\:fnh4OuAh1KEiMctPuUoep)
- [Live](docId\:fnh4OuAh1KEiMctPuUoep)
- [Paused](docId\:fnh4OuAh1KEiMctPuUoep)
- [Stale](docId\:fnh4OuAh1KEiMctPuUoep)
- [Archived](docId\:fnh4OuAh1KEiMctPuUoep)

### Draft

The flag is still in the configuration phase and does not serve traffic in any environment. Each newly created ruleset (which includes the flag's environment and rules) starts in **Draft** status. The following conditions determine this status:

- **Ruleset environment** – Production (Primary environment) and Non-production (Development).
- **Ruleset status** – Draft
- **Rule status** – Any or none.
- **Last modified** – Any

### Testing

The flag is actively tested in Non-production environments only. Review the results before promoting to Production. The following conditions determine this status:

- **Ruleset environment** – Production (Primary environment) and Non-production (Development).
- **Ruleset status** –
  - **Production (Primary Environment)** – Draft or Paused
  - **Non-Production (Dev)** – Running
- **Rule status** –
  - **Production (Primary Environment)** – Any status or no rules.
  - **Non-Production (Dev)** – At least one Running rule.
- **Last modified** – Any

### Live

The flag is active in Production and serving traffic. This includes flags with running experiments or recently concluded experiments still being observed. The following conditions determine this status:

- **Ruleset environment** – Production (Primary environment) and Non-production (Development).
- **Ruleset status** – At least one Running ruleset in Production.
- **Rule status** – At least one Running rule in Production.
- **Last modified** – Any

### Paused

The flag is paused and is not serving new traffic. The following conditions determine this status:

- **Ruleset environment** – Production (Primary environment) and Non-production (Development).
- **Ruleset status** – Paused
- **Rule status** – Any or none.
- **Last modified** – Any

### Stale

The flag is no longer in active use and is a candidate for cleanup or archiving. Flags that have not been modified for more than 30 days and are not delivering traffic enter this state. The following conditions determine this status:

- **Ruleset environment** – Production (Primary environment) and Non-production (Development).
- **Ruleset status** – Any status other than Running.
- **Rule status** – Any or none.
- **Last modified** – Last modified more than 30 days ago.

Use the **Stale** status to identify flags that are ready for removal or archiving.

### Archived

Archive flags that are no longer needed. Archiving a flag also removes it from the [datafile](docId:3LmHm4b3kTxKBuoR93KN8) (the JSON configuration file Feature Experimentation uses to deliver flag rules to your application).

:::hint{type="info"}
**Note**

Optimizely Feature Experimentation keeps your flag and rule data so you can unarchive the flag later.
:::

## Filter by flag status

1. Go to **Flags**.
2. Click **Apply Filters**.

   ![Screenshot of the Flags page with the Apply Filters highlighted](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/UZvkEYzcehy5FHUUoNGvH-20260720-145743.png)
3. Click **+ Add Filter**.
4. Use the field drop-down list and select **Status** in the **Flag** section.

   ![Screenshot of the filter field drop-down list with Status selected in the Flag section](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/2OT5hGmV6ZTYlP1wuRQ7x-20260720-145743.png)
5. Use the operator drop-down list and select **is**.
6. Select the statuses you want to filter by using the value drop-down list.

## Flag history

Every flag has its own change history. Complete the following steps to view a flag's change history:

1. Go to **Flags**.
2. Click a flag.
3. Click **History**.
4. Use **Type** drop-down list and select **Flag**.

   ![Screenshot of the flag History page with the Type drop-down list set to Flag](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/0LwOCirR94dFhYSgJ-BlD-20260720-145743.png)

The flag's change history works similarly to the [project's change history](docId\:laL7T8HQ8_tSdtSya2VWb). Use the drop-down lists to filter by **Type**, **Date**, and **Source**.

To expand all change details, press Alt (Windows) or Option ⌥ (Mac) and click **Show details**. To collapse all, press the same keys and click **Hide details**.

See [Flag history](docId\:laL7T8HQ8_tSdtSya2VWb) for a full list of tracked change types.