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
      • Required comments
      • Required confirmation
      • Scheduled flag changes
      • Workflows
        • Creating workflows
        • Deleting workflows
        • Workflow templates
    • 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
  • About workflows
  • Use cases for workflows
  • Prerequisites
  • Create workflows
  • Permissions in workflows
ReleasesRelease management tools

Workflows

Was this page helpful?
Previous

Creating workflows

Next
Built with
Workflows are in maintenance mode

The Workflows feature is in maintenance mode, and is planned for future deprecation at a date not yet specified. We will work with existing customers using workflows to migrate to a replacement solution when deprecation occurs.

You cannot use LaunchDarkly workflows with the ServiceNow integration or custom approvals

You cannot use workflows in any environment that uses the ServiceNow integration or custom approvals. Workflows are still available in other environments that don’t use ServiceNow or custom approvals.

Overview

This topic explains how to build, start, and view workflows in LaunchDarkly. A workflow is a set of actions that you can schedule in advance to make changes to a feature flag.

About workflows

Workflows can automate some of the manual tasks required to manage a feature flag. These tasks often take place in stages. For example, a feature flag workflow that gradually releases a flag to more contexts might look like this:

A workflow that progressively rolls out a flag over time.

A workflow that progressively rolls out a flag over time.

Workflows support consistent release practices and let you automatically release a feature based on your release process.

You can also use the REST API: Workflows

Use cases for workflows

You can set up three kinds of workflows, which correspond to three common use cases: progressive rollout workflows, maintenance window workflows, and custom workflows.

If you are interested in gradually rolling out a particular flag variation to more contexts over a defined period of time, we recommend that you use the separate progressive rollout feature instead of setting up a progressive rollout workflow.

Progressive rollouts are an option on a flag’s targeting rule to serve a given flag variation to a specified percentage of contexts, and gradually increase that percentage over a specified time. They are a built-in feature that supports the most common use case for workflows. We recommend using progressive rollouts instead of workflows if they meet your needs, because progressive rollouts are easier to set up, and because the flag variation that any particular customer encounters changes only once over the course of the rollout. To learn more, read Progressive rollouts.

Prerequisites

To use workflows, you should understand the following features:

  • Approvals
  • Scheduled flag changes

Create workflows

Read the following topics to learn how to create different kinds of workflows:

  • Progressive rollout workflows gradually increase the percentage of contexts targeted by a flag.
  • Maintenance windows let you temporarily toggle targeting on or off.
  • Custom workflows manage a specific rollout process that you define.

You can also save a workflow as a template to reuse later. To learn how, read Workflow templates.

Permissions in workflows

A LaunchDarkly member must have permission to make flag changes to create workflows because workflows inherit permissions from flags. To learn more about how to configure the right permissions for members, read Resources.