Skip to content
feat.so feat.so

Scheduled changes

A scheduled change is a flag-config edit that you write today and apply at a specific point in the future. The dashboard records the change, and feat applies it when the time arrives.

When to use them

Section titled “When to use them”
  • Coordinated launches. Turn a flag on at exactly 10:00 UTC across all your services without humans in the loop.
  • Off-hours changes. Schedule a flag flip for a quiet maintenance window without needing someone awake to push the button.
  • Time-bound features. Turn a holiday banner on at midnight on December 1, off at midnight on December 26.

For a sequence of changes that depend on each other (approve, wait, apply), use Workflows. For a single dated change, scheduled changes are the lighter tool.

Creating one

Section titled “Creating one”

Open the flag in the environment you want to change. Pick Schedule a change. Specify:

  • The scheduled time (timezone defaults to your organization’s; the dashboard converts).
  • The change: the same shape you would otherwise submit directly (turn targeting on, change the default rule, adjust a rollout, etc.).
  • Optionally, a comment: stored in the audit log when the change applies.

Save. The change appears in the pending list for that flag in that environment.

What happens at scheduled time

Section titled “What happens at scheduled time”

At scheduled time feat:

  1. Re-validates the payload against the current flag shape (variations may have been added or renamed since the change was scheduled).
  2. Applies it.
  3. Writes an audit log entry attributed to system with a reference to the original scheduled change.
  4. Sets the status to applied, or failed if validation fails. A failed change does not retry; you cancel it and reschedule.

Cancelling

Section titled “Cancelling”

A pending scheduled change can be cancelled at any time before its scheduled time. Cancelled changes leave an audit entry.

Combined with approvals

Section titled “Combined with approvals”

If the environment requires approval, scheduling a change still goes through review. The flow:

  1. You schedule the change. The system creates a change request whose payload is the scheduled change.
  2. Reviewers approve.
  3. At scheduled time, the system applies the change (the approval has already cleared it).

If the change has not been approved by scheduled time, it does not apply. It stays pending until someone approves and applies it, or until it expires.

Org-level setting

Section titled “Org-level setting”

Scheduled changes are off by default per organization. An admin enables them from Organization features. When off, the “Schedule a change” action is hidden.

Section titled “Related”