Loading
Salesforce now sends email only from verified domains. Read More
Automate Your Business Processes
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
            Log Flow Data Persistently to Data 360

            You are here:

            1. Salesforce Help
            2. Docs
            3. Automate Your Business Processes

            Log Flow Data Persistently to Data 360

            Log flow run metrics persistently to Data 360, ensuring reliable and scalable data management. Set up persistent logging for record-triggered, platform event-triggered, schedule-triggered flows, and autolaunched flows.

            Required Editions

            View supported editions.
            User Permissions Needed
            To log flow data to Data 360: View All Data
            Note
            Note Turning on flow logging consumes Data 360 credits. See Billing Impact of Data 360-Powered Features and Data 360 Billable Usage Types.
            1. Open your flow.
            2. Click View properties then click Show Advanced.
            3. Click Set Up Persistent Logging for this Org.
            4. After setup, select Enable persistent logging for this flow.
            5. Save your flow.
              Set up persistent logging for each new flow version and new flow.

            To view the flow data, build standard Salesforce reports on flow performance using the FlowRun and FlowElementRun custom report types for deep insights. You can also use Data Explorer to view the Flow Run or Flow Run Element data model object (DMO).

            • Subflow element executions are logged regardless of whether the referenced flow has persistent logging enabled.
            • The flow and element execution times are calculated in milliseconds.

            A flow run isn’t logged to Data 360 if:

            • The flow is run using debug in Flow Builder.
            • An Apex test or flow test runs the flow.

            Multiple flow run records appear for a single flow execution due to asynchronous and scheduled paths creating separate flow interviews. For example, a flow with immediate, asynchronous, and scheduled paths generates three flow run records. Multiple flow element run records appear for a single flow execution with transaction boundaries, including wait elements that pause, resume, and complete, or asynchronous action elements.

            See Also

             
            Loading
            Salesforce Help | Article