No results for ""
EXPAND ALL
  • Home
  • API docs

GIVE DOCS FEEDBACK

Release flags

Read time: 2 minutes
Last edited: Mar 04, 2024

Overview

This topic explains how you can use release flags to progressively roll out functionality. Release flags are temporary flags that initially do not serve the new functionality, then progressively roll out the functionality until they reach 100%.

Understanding release flags

Release flags, sometimes called rollout flags, are temporary boolean flags with two variations: "Available" (true) and "Unavailable" (false).

In the most common use case, you wrap a release flag around code for a new or improved feature, and use the flag to release the new feature to your customers in increments. Release flags are temporary. After you verify the new code is stable and roll out the feature to 100% of your customers, you should delete the flag.

To create a release flag:

  1. Navigate to the flags list.
  2. Click Create flag.
  3. Choose Release:
The "Configuration" section of the "Create new flag" page.
The "Configuration" section of the "Create new flag" page.

To learn more, read Creating new flags.

Because release or rollout flags are used to release a new feature in increments, they typically do not use complex targeting rules. Instead, they serve a percentage rollout in their default rule. To learn more, read Percentage rollouts.

If you have a well-defined process for releasing new features gradually, we recommend using a workflow with your release flag. A workflow is a set of actions that you can schedule in advance to make changes to a feature flag. For a release flags, you can schedule a gradual increase in the percentage of contexts targeted by the flag. To learn more, read Workflows.