Turn a feature off immediately

Overview

To turn a feature off for everyone, make the flag serve false in that environment: set Fallthrough to false and remove any rules that serve true. SDK clients pick up the change within seconds when streaming is on, or on their next poll.

Turn it off

Open the flag

In the dashboard, open the project, click the flag (for example new-checkout), and select the environment, for example production.

Serve false

Set Fallthrough to false. Remove every rule that serves true, or change its Serve to false.

Save

Click Save environment.

Switching Enabled in production off does not turn a boolean flag off by itself. A disabled flag skips its rules and serves the Fallthrough value to everyone. If Fallthrough is true, a disabled flag keeps serving true. Always set Fallthrough to the off value.

Switching Enabled in <environment> off is still useful when Fallthrough is already false: it stops every rule from matching in one click, without deleting the rules.

How fast it takes effect

Client setup	Time to see the change
TypeScript: `stream: true`	Normally within seconds when a WebSocket implementation is available. The notification triggers a snapshot fetch; polling continues as a backup unless disabled.
TypeScript: polling only	Next successful poll: `refreshIntervalMs` (default 30 seconds) after the previous fetch finishes, plus fetch time. Failures can delay it further.
TypeScript: `refreshIntervalMs: 0` without `stream: true`	Only on manual `refresh()` or restart. Don’t use this for flags you may need to kill.
Go: polling	Next successful poll on the `RefreshInterval` schedule (default 30 seconds), plus fetch time. Slow or failed requests can delay it further.
Go: `DisablePolling: true`	Only on manual `Refresh(ctx)` or restart.

// src/lib/shipd.ts
export const shipd = createClient<FlagDefinitions>({
  sdkKey: process.env.SHIPD_SDK_KEY!,
  stream: true,
  defaults: { "new-checkout": false },
});

// flags.go
client, err := shipd.New(shipd.Options{
    SDKKey: os.Getenv("SHIPD_SDK_KEY"),
    RefreshInterval: 5 * time.Second,
    Defaults: map[string]any{"new-checkout": false},
})
if err != nil { return err }
defer func() {
    ctx, cancel := context.WithTimeout(context.Background(), 2*time.Second)
    defer cancel()
    if err := client.Shutdown(ctx); err != nil { log.Printf("shipd events: %v", err) }
}()

See Local evaluation for how snapshots refresh.

Make the code default the safe value

When the SDK has no snapshot (before ready(), or when the edge is unreachable with no cache), it serves the client defaults. Write flags so the default is the safe state:

// Good: false means the risky path is off
if (shipd.isEnabled("new-checkout", { userId })) {
  return renderNewCheckout();
}
return renderLegacyCheckout();

if client.IsEnabled("new-checkout", shipd.EvaluationContext{UserID: userID}) {
    return renderNewCheckout()
}
return renderLegacyCheckout()

Keep default: false in your flag definitions too. shipd push sets Fallthrough in the target environment to the config default, so a config that says true would turn the feature back on at the next push.

Approvals

If an approval policy protects the environment, Save environment can create a pending request instead of changing the live flag. The feature stays on until the request is approved. Plan for this before an incident: make sure enough reviewers are available, or keep a policy that lets on-call staff approve quickly.

Flags

Config as code

Operations

Enterprise

Migrate to shipd

Turn a feature off immediately

Overview

Turn it off

How fast it takes effect

Make the code default the safe value

Approvals

​Overview

​Turn it off

​How fast it takes effect

​Make the code default the safe value

​Approvals

​Related

Overview

Turn it off

How fast it takes effect

Make the code default the safe value

Approvals

Related