For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
      • The Flags list
      • Comparing and copying flag settings
      • Viewing flags across environments
      • Deprecating flags
      • Archiving flags
      • Deleting flags
      • Flag prerequisites
      • The off variation
      • The default rule
      • Flag statuses and lifecycle stages
      • Flag lifecycle settings
      • Project-level flag settings
      • Vega for flag cleanup
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Set the off variation
Feature flagsManage flags

The off variation

Was this page helpful?
Previous

The default rule

Next
Built with

Overview

This topic explains how to set the off variation for a flag.

When the toggle is turned off, LaunchDarkly serves the default off variation for your feature flag. For boolean flags, the default off variation is set to false, but you can change this if you like. For multivariate flags, you select one of your custom variations.

The off variation is different from the default rule. The default rule determines which variation a flag serves, when toggled on, to contexts that don’t match any of the flag’s previous targeting rules. To learn more, read The default rule.

The off variation is also different from the fallback value. The fallback value is the value that contexts receive if your application cannot connect to LaunchDarkly. To learn more, read Fallback value.

Set the off variation

You can customize the default off variation for both boolean and multivariate flags on each flag’s Targeting tab, or in your flag templates. To learn more, read Flag templates.

If you do not specify a default off variation, then the SDK will return the fallback value defined in your code when the flag is off.

You can also use the JSON editor

To learn how to set the off variation using JSON, read Off variation.

Setting a fallback value in your SDK call

Regardless of how you set up targeting for your feature flag, each time you evaluate a flag from the SDK, you must include a fallback value as one of the parameters. This fallback value is the value served to the context if the SDK cannot connect to LaunchDarkly. To learn more, read Evaluating flags.