Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Extend Salesforce with Clicks, Not Code
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Considerations and Limitations for Flows in Lightning Pages

            You are here:

            1. Salesforce Help
            2. Docs
            3. Extend Salesforce with Clicks, Not Code

            Considerations and Limitations for Flows in Lightning Pages

            Here are some things to keep in mind when you add a flow component to a Lightning page.

            Required Editions

            Available in: both Salesforce Classic and Lightning Experience
            Available in: Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions

            Lightning pages always use Lightning runtime, so also review Limitations of Lightning Runtime for Flows.

            • Running Flows from a Lightning Page—When a user opens a Lightning page that has a flow component, the flow runs when the page loads. Make sure that the flow doesn’t perform any actions, such as create or delete records, before the first screen.
            • Input Variable Limitations—These variables aren’t supported.
              • Collection variables
              • Record variables
              • Record collection variables
            • The component supports only manually entered values for input variables.
            • Text input variables accept a maximum length of 4,000 characters.
            • Deployment Considerations—Change sets and the Metadata API deploy all flows as inactive, which users can’t run. If you deploy a Lightning page (known as FlexiPage in the API) that contains a flow component, make sure to activate the flow.
             
            Loading
            Salesforce Help | Article