Add Scheduled Rollouts concept page - #39056
Open
NatachaMaly wants to merge 2 commits into
Open
Conversation
Document scheduling a targeting rule to start automatically at a future date and time, including how it interacts with progressive rollout starts, editing/completion locks, and the approval workflow.
jeff-morgan-dd
requested changes
Aug 10, 2026
jeff-morgan-dd
left a comment
jeff-morgan-dd
left a comment
Contributor
There was a problem hiding this comment.
Thank you for the PR! Please see some small edits and suggestions inline.
|
|
||
| Instead of activating a targeting rule immediately, you can schedule it to start automatically at a future date and time. This is available for both [feature gates](/feature_flags/concepts/targeting_rules/#targeting-rule-types) and [progressive rollouts](/feature_flags/concepts/targeting_rules/#targeting-rule-types). | ||
|
|
||
| A feature gate normally starts as soon as you save it. A [progressive rollout](/feature_flags/use_cases/progressive_rollouts/#start-and-control-the-rollout) normally requires you to click **Start Rollout** to begin. When you schedule a start time on either rule type instead, it activates automatically at that time, you don't need to click **Start Rollout** (for a progressive rollout) when the scheduled time arrives. |
Contributor
There was a problem hiding this comment.
Suggested change
| A feature gate normally starts as soon as you save it. A [progressive rollout](/feature_flags/use_cases/progressive_rollouts/#start-and-control-the-rollout) normally requires you to click **Start Rollout** to begin. When you schedule a start time on either rule type instead, it activates automatically at that time, you don't need to click **Start Rollout** (for a progressive rollout) when the scheduled time arrives. | |
| A feature gate normally starts as soon as you save it. A [progressive rollout](/feature_flags/use_cases/progressive_rollouts/#start-and-control-the-rollout) normally requires you to click **Start Rollout** to begin. When you schedule a start time on either rule type instead, it activates automatically at that time. |
| {{< img src="feature_flags/concepts/schedule-a-rollout-start.png" alt="Targeting Rule editor side panel on a feature flag with a scheduled start." style="width:70%;" >}} | ||
|
|
||
| <div class="alert alert-info"> | ||
| If the flag is disabled in the environment, a message appears. Enable the flag before the scheduled rollout for it to take effect. |
Contributor
There was a problem hiding this comment.
Suggested change
| If the flag is disabled in the environment, a message appears. Enable the flag before the scheduled rollout for it to take effect. | |
| If the flag is disabled in the environment, the rule will not run. Enable the flag before the scheduled rollout for it to take effect. |
|
|
||
| ## Approve a rollout whose start time has passed | ||
|
|
||
| If a scheduled rule change requires [approval](/feature_flags/concepts/approvals/), the rollout does not start automatically while the change is still pending. If the scheduled start time passes before a reviewer approves it, the rollout does not start silently, see [Approve, reject, or apply](/feature_flags/concepts/approvals/#approve-reject-or-apply) for details. |
Contributor
There was a problem hiding this comment.
Suggested change
| If a scheduled rule change requires [approval](/feature_flags/concepts/approvals/), the rollout does not start automatically while the change is still pending. If the scheduled start time passes before a reviewer approves it, the rollout does not start silently, see [Approve, reject, or apply](/feature_flags/concepts/approvals/#approve-reject-or-apply) for details. | |
| If a scheduled rule change requires [approval](/feature_flags/concepts/approvals/), the rollout does not start automatically while the change is still pending. If the scheduled start time passes before a reviewer approves it, the rollout does not start. See [Approve, reject, or apply](/feature_flags/concepts/approvals/#approve-reject-or-apply) for details. |
jhgilbert
added
the
astro-reorg-no-conflicts
Contributor
Address review feedback on scheduled_rollouts.md and add the page to the Concepts sidebar navigation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Adds a new "Scheduled Rollouts" concept page documenting how to schedule a targeting rule (feature gate or progressive rollout) to start automatically at a future date and time. Covers:
Also updates
targeting_rules.md(links out to the new page instead of duplicating the walkthrough, updates the rule type table),approvals.md(documents the Cancel/Start Now confirmation modal for overdue scheduled approvals),progressive_rollouts.md(cross-links to scheduling as an alternative to manually clicking Start Rollout), and the Concepts nav index.Merge readiness
AI assistance
Drafted with Claude Code: page structure/content, cross-linking, and a self-review pass that caught and fixed several consistency issues (duplicate content, contradictory behavior descriptions, misplaced approval details).