Skip to content
Featureflip Docs

Scheduled Changes

Scheduled changes let you queue a flag to turn on or off automatically at a future time, instead of logging in at the exact moment to flip it yourself. You set the target state and the time up front, and Featureflip applies the change on the server when it arrives — so a timed launch, an end-of-promotion cutoff, or a middle-of-the-night maintenance window becomes something you set once and forget.

Scheduled changes are set per flag, per environment. A change you queue in Production has no effect on Staging.

Scheduling a change

Section titled “Scheduling a change”
  1. Open the flag from your project’s Flags page.
  2. Select the environment tab where you want the change to happen (for example, Production).
  3. Click Schedule… next to the environment’s on/off control.
  4. In the Schedule on/off change dialog:
    • Target state — choose Turn ON or Turn OFF.
    • When — pick the date and time, entered in your local time. The time must be in the future; Featureflip will not accept a moment that has already passed.
  5. Click Schedule.

Your change is now queued. It does nothing to the live flag until the time you chose arrives.

Viewing pending and recent changes

Section titled “Viewing pending and recent changes”

Each environment shows a Scheduled changes panel on the flag:

  • Pending — changes that are queued but have not applied yet. Each row shows the target state (Turn ON / Turn OFF), the time it will apply in your local time, and who scheduled it.
  • Recent — the last few changes that have already resolved, each with a status of Applied, Cancelled, or Failed. A failed change shows the reason it could not be applied.

Cancelling a scheduled change

Section titled “Cancelling a scheduled change”

You can cancel any change while it is still Pending:

  1. Find the change in the Pending list of the flag’s Scheduled changes panel.
  2. Click Cancel on that row.
  3. Confirm in the dialog.

The change moves to Cancelled and will never apply. To change the target state or timing of a pending change, cancel it and schedule a new one with the details you want.

Once a change has already applied, it is part of the flag’s history and shows as Applied — it is not something you can undo from here. To reverse it, flip the flag again or schedule a new change.

What happens when a change applies

Section titled “What happens when a change applies”

At the scheduled time, Featureflip re-runs the same flag change you would have made by hand. Because it goes through the normal change path rather than a separate one:

  • It streams to your SDKs. The new flag state propagates to every connected SDK over its streaming connection within seconds — no redeploy or restart.
  • It is recorded in the audit log under the person who scheduled it, so your flag history shows who queued the change and when it took effect, not an anonymous system entry.
  • The rest of evaluation is unchanged. Scheduling sets whether a flag is on, not how it evaluates. When the flag turns on, your targeting rules, segments, rollout percentage, and prerequisites all still apply exactly as they would after a manual toggle.
  • Failures are visible. If something blocks the change when it is due, it is marked Failed with a reason rather than silently skipped.

Common patterns

Section titled “Common patterns”
  • Timed launch. Schedule a flag to turn ON at your announcement time so the feature goes live exactly when planned, even if nobody is at a keyboard.
  • Maintenance window. Schedule one change to turn a flag OFF at the start of the window and a second change to turn it back ON at the end. Each is independent, and you can cancel or reschedule either side without touching the other.
  • End-of-promotion cutoff. Schedule a limited-time feature to turn OFF the moment the promotion ends.
  • Off-hours cutover. Set up a 2am flip from your desk during the working day and log off — the change runs on its own.

Next steps

Section titled “Next steps”