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

GIVE DOCS FEEDBACK

Scheduled flag changes

Read time: 6 minutes
Last edited: Jan 26, 2024
Scheduled flag changes is an Enterprise feature

Scheduled flag changes is available to customers on an Enterprise plan. To learn more, read about our pricing. To upgrade your plan, contact Sales.

Overview

This topic explains how to schedule flag changes to take effect at a date in the future.

Scheduling flag changes lets you define and schedule changes to your flag’s targeting rules for future points in time. You can create a progressive delivery strategy by scheduling the incremental steps to release your feature to 100% of your user base.

For example, you can schedule a feature to turn on for internal testing two days from today, then enable it for your ‘beta’ customer segment four days later, and finally start an automated rollout increasing to 100% over the following five days.

You can configure scheduled flag change permissions with custom roles

You can create a custom role policy to allow or deny it to make scheduled flag changes. To learn more about custom roles actions for this feature, read Using actions.

You can also use the REST API: Scheduled changes

Benefits of scheduling flag changes

Benefits of scheduling flag changes include:

  • Timing an early launch: Scheduling your flag to turn on or off on a specified date/time lets you plan your release without having to manually make changes at desired release times.
  • Progressive feature rollouts: This functionality lets you create a set of scheduled changes to your flag once, and LaunchDarkly slowly release the feature for you. For example, you can schedule your flag to roll out to 20% of your user base tomorrow, 35% the day after, 50% the day after that, and increase that percentage until it reaches 100%.
  • Temporary access: You can schedule rules that target certain contexts and segments to be added to or removed from your flag’s targeting to better manage customer access.
  • Flag hygiene: You can schedule your flag’s targeting rules to clean up once your flag has been rolled out to 100% of your user base.

Creating scheduled flag changes

To schedule a set of flag changes:

  1. Navigate to the flags list and select the flag for which you want to schedule targeting changes. The flag's Targeting tab appears.
  2. Make the changes you want to the flag’s targeting.
  3. Click the dropdown icon in the Review and save button and select "Schedule changes":
The "Schedule changes" option below the "Review and save" button.
The "Schedule changes" option below the "Review and save" button.
  1. In the "Schedule" section, select a date, time, and timezone for when you want the changes to execute, or click on the calendar icon to expand a calendar view:
The change scheduling calendar.
The change scheduling calendar.
  1. Click Apply.
  2. Review and confirm the changes displayed in the dialog.
  3. If your environment requires approvals for flag changes, enter a description and choose one or more reviewers.
  4. (Optional) Enter a comment.
  5. Click Schedule changes.

Your changes have now been scheduled.

You can schedule multiple changes for different dates and times for a single flag. For example, you can implement a progressive rollout strategy by scheduling multiple sequential changes to targeting rules.

Here is an image of a flag with multiple changes scheduled:

A flag with multiple changes scheduled.
A flag with multiple changes scheduled.

If you use scheduled flag changes to schedule context removal dates, but an approver approves the request after the scheduled date and time of the context removal, LaunchDarkly prevents you from applying the change. To learn more about scheduling, read Scheduling context removal from segments.

You can also use the REST API: Create scheduled changes workflow.

Creating scheduled flag changes that require approvals

Enterprise customers can require approvals for scheduled flag changes. If approvals are required, the change is marked "Pending Review" in the "Pending changes" panel.

If there are conflicts between changed flags and requested changes, approved and applied changes take precedence over pending or requested changes. To learn more, read Managing conflicts with scheduled changes.

Viewing scheduled flag changes

To view all the scheduled changes for a flag:

  1. Navigate to the flags list and select the flag for which you want to view the scheduled changes. The flag's Targeting tab appears.
  2. The number of scheduled changes appear in the upper right corner:
The number of pending changes for a flag.
The number of pending changes for a flag.
  1. To view the complete list of changes, click on the clock icon. A panel appears that displays all the pending changes that are scheduled for this flag. The changes are listed chronologically, with the earliest upcoming change listed first.

You can also use the REST API: List scheduled changes.

Updating scheduled flag changes

To update a scheduled flag change:

  1. Follow the steps in Viewing scheduled flag changes to open the list of pending scheduled changes for the flag.
  2. Find the scheduled change you wish to update.
  3. Click on the overflow menu in the upper right and choose "Edit":
The "Edit" option in a pending change's overflow menu.
The "Edit" option in a pending change's overflow menu.
  1. A dialog appears with the list of scheduled flag changes.
  2. Update the date or time for these changes.
  3. (Optional) Enter a comment.
  4. Click Update scheduled change.

You can also use the REST API: Update scheduled changes workflow.

Deleting scheduled flag changes

To delete a scheduled flag change:

  1. Follow the steps in Viewing scheduled flag changes to open the list of pending scheduled changes for the flag.
  2. For the scheduled change you wish to delete, click on the overflow menu in the upper right and choose "Delete":
The "Edit" and "Delete" options for a pending change.
The "Edit" and "Delete" options for a pending change.

You can also use the REST API: Delete scheduled changes workflow.

Managing conflicts with scheduled changes

It’s possible that as you schedule a change to a flag, another member introduces a breaking change, or a conflict.

Conflicts occur for two reasons:

  • Another member updated the flag’s targeting that invalidates one or more of your scheduled changes
  • Another member scheduled a set of conflicting changes to be executed before your changes

LaunchDarkly warns members in the user interface (UI) when they save or schedule changes to the flag that introduce conflicts with other pending scheduled changes.

Here is an image of the Confirm changes dialog with a conflict:

A notification showing a conflicting scheduled change.
A notification showing a conflicting scheduled change.

Despite this warning, a member could decide to save their conflicting changes anyway. If this happens, LaunchDarkly sends an email notification to the member whose changes now conflict. That member's changes will not take effect at the time and date they were scheduled to.

Resolving conflicts in scheduled changes

If your scheduled changes conflict with other changes, you receive an email notification.

You can resolve the conflict and ensure your scheduled changes don’t fail in one of two ways:

  • Choose one of the two conflicting changes and delete the other. For example, you may have scheduled three targeting rules to be updated and someone deletes one of those rules, which causes a conflict. If this happens, you can update your scheduled changes to delete the scheduled changes to that rule. This ensures that the conflict is resolved and the remaining rules are updating successfully.
  • Update the conflicting changes so they no longer conflict. You can update your changes or the new scheduled changes to resolve the conflict and ensure both scheduled changes execute successfully.