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
    • 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
      • Approvals
      • Flag triggers
        • Creating flag triggers
        • Managing flag triggers
      • Required comments
      • Required confirmation
      • Scheduled flag changes
      • Workflows
    • 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
  • Manage existing flag triggers
ReleasesRelease management toolsFlag triggers

Managing flag triggers

Was this page helpful?
Previous

Required comments

Next
Built with

This topic explains how to disable, reset, and delete flag triggers.

Manage existing flag triggers

You can modify existing triggers from the flag’s environment-specific settings page. After you create a trigger, you can disable, reset, or delete it.

To modify an existing trigger:

  1. Navigate to the feature flag for which you wish to edit a trigger.
  2. Click on the three-dot overflow menu for the environment you want to edit a trigger in.

The environment overflow menu.

The environment overflow menu.
  1. Select Configuration in environment. The “Environment configuration” screen appears.
  2. Find the trigger you wish to modify and click the overflow menu. The trigger options appear:

The overflow menu, expanded.

The overflow menu, expanded.
  1. Choose the option you wish from the options menu:
  • Disable trigger: If you choose this option, the trigger configuration is saved but the trigger stops working. To re-enable the trigger, open the overflow menu and choose “Enable trigger.”
  • Reset trigger URL: If you choose this option, LaunchDarkly generates a new URL for this trigger. Use this option if you lose a URL for an existing trigger. You must update any clients using this URL to use the new URL. Type the trigger’s type and click Reset to confirm.
  • Delete trigger: If you choose this option, the trigger and its URL are deleted permanently. Type the trigger’s type and click Delete to confirm.

You can also use the REST API: Update flag trigger, Delete flag trigger