Skip to content
feat.so feat.so

Workflows

A workflow is an ordered sequence of steps that describes a multi-step release: “wait for approval, then wait until Tuesday morning, then apply this change.” The system advances through the steps automatically as each one becomes ready.

When to use a workflow

Section titled “When to use a workflow”

Use a workflow when a single dated change is not enough:

  • Approval then schedule then apply. A reviewer signs off, the system waits until the launch window, then applies.
  • Stage gates. Bake for 24 hours in 1% traffic, then approval, then move to 10%.
  • Coordinated multi-flag releases. A workflow per flag, scheduled together.

For a single dated change with no other gates, Scheduled changes is the simpler tool. For “approve before apply” with no schedule involved, use a plain Change request.

Step types

Section titled “Step types”

A workflow is built from three step kinds:

StepWhat it does
ApprovalPauses until N reviewers approve.
SchedulePauses until a specific point in time (absolute timestamp or relative delay).
ApplyApplies a flag-config change. Always the last step.

Constraints the dashboard enforces:

  • The workflow must end in an Apply step.
  • Approval steps must come before Schedule steps within a single workflow.
  • A workflow can mix and reorder Approval and Schedule steps, but Apply is always last.

The flow

Section titled “The flow”
  1. Create. You define the steps in the dashboard. The workflow starts in pending.
  2. Advance. feat advances the workflow whenever the current step’s readiness condition is met. Approval steps become ready when enough approvals are collected. Schedule steps become ready when their time arrives.
  3. Apply. When advancement reaches the Apply step, the system applies the change. Status becomes completed.
  4. Halt. You can halt a workflow at any time. Reason is recorded. A halted workflow does not auto-resume; you cancel it and start a fresh one.

Worked example

Section titled “Worked example”

A workflow that mirrors a typical regulated production release:

Step 1  Approval     wait for 2 approvals
Step 2  Schedule     wait until 2026-07-15 09:00 UTC
Step 3  Apply        turn on targeting, set default rule to "true"

You create this on a Friday. Two teammates approve over the weekend (step 1 clears). The workflow waits through Monday and Tuesday. At 09:00 UTC Wednesday, the system applies the change. Audit log shows the apply attributed to system, with references to the workflow ID and to each of the approval entries.

Org-level setting

Section titled “Org-level setting”

Workflows are off by default per organization. An admin enables them from Organization features.

Section titled “Related”