---
schema_version: "1"
id: dae8ef7a6b85d372f882785cf838a6344e024ffe1417f3e1091912a310ca409b
title: Change Set Considerations for Flows
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/flow_considerations_change_sets.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_considerations_change_sets.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f58fe3947f2291423f4c4eaded7e79278d9df6e07e812e5363045561d1480248
description: Before you use change sets to deploy a flow, understand the limits and behaviors that are related to component dependencies, deployment, and flow triggers.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Change Set Considerations for Flows

Before you use change sets to deploy a flow, understand the limits and behaviors that are related to component dependencies, deployment, and flow triggers.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=platform.flow_ref_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Learn about the editions and user interfaces that support Flow Builder. Some Flow Builder features integrate with other Salesforce products that require additional licenses.">View supported editions.</a></td></tr></tbody></table>

## Creating Change Sets

- If you want to deploy a flow with a change set, the change set must include any component the flow references.
- When you view the dependent components for the change set, the Component Dependencies page lists the dependencies for _all_ versions of the flow. Add all interdependent components for the relevant flow version to the outbound change set.
- If a flow element references these components, the Component Dependencies page doesn’t display that component. To deploy the flow successfully, manually add those referenced components to the change set.
    - Post to Chatter
    - Send Email
    - Submit for ApprovalFor example, if you deploy a flow that includes a Submit for Approval element, manually add the referenced approval process.
- If a flow references a Lightning component that depends on a CSP Trusted Site, the trusted site isn’t included in the package or change set.

## Deploying Change Sets

- You can include only one version of a flow in a change set.
- An active flow in a change set is deployed to its destination as inactive. Manually activate the flow after deployment.
- If the flow has no active version when you upload the outbound change set, the latest inactive version is used.
- Deploying or redeploying a flow with a change set creates a version of the flow in the destination Salesforce org.
- In production orgs, you can enable the setting to deploy a new active version of a process or flow using change sets or Metadata API. The setting doesn’t appear in non-production orgs (such as scratch, sandbox, and developer orgs), because you can always deploy a new active version.

## Flow Triggers

- Flow triggers aren’t available in change sets.

#### See Also

- [Deploy Processes and Flows as Active](https://help.salesforce.com/s/articleView?id=platform.flow_distribute_deploy_active.htm&release=264.0.0&type=5 "By default, processes and flows that are active in a sandbox or non-production org are deployed to a production org as inactive. After deployment, manually reactivate the new versions. In production orgs, you can enable the setting to deploy a new active version of a process or flow via change sets or Metadata API. If you use a continuous integration and continuous delivery model to deploy metadata changes, enable the option to deploy processes and flows as active.")