Schedule a change

A launch that happens at 9:00 sharp — not “when someone got to their desk” — is one of the quiet joys of feature flags. You can schedule a flag’s state to change at a time you pick, and then go do something else.

Schedule it

Open your flag in the environment you’re launching in, and instead of toggling it now, choose to schedule the state change: pick on or off, pick the time, confirm. The dashboard shows the upcoming change on the flag until it happens.

Scheduling takes the same permission as toggling the environment right now — a schedule is just a write with a timestamp, so production-class environments hold it to the same bar.

What happens at T

The change takes effect at exactly the chosen time, for every reader at once. There’s no minute-by-minute drift between devices that polled at different moments: a device asking at T-1 second gets the old value, at T+1 second the new one. The moment it fires, it stops showing as upcoming — what you see on the flag is always what’s true.

What can be scheduled

On/off state changes for boolean flags. Targeting rules and multivariate defaults can’t be scheduled — those changes happen when you save them. If you need a rules change at 9:00, that’s a calendar reminder and a saved draft of your intent — or a proposal approved at 9:00.

Where to next

• Roles and safety — the permission model schedules follow
• Export the audit log — scheduled changes land there like any other
• Set up a percentage rollout — the gradual alternative to a hard launch