Analyze Screen Flow Usage

We set up a new Sample Flow Report: Screen Flows custom report type and report for you. See who’s running the screen flows you build. Discover flow interview execution counts and screen duration times. Review the status of a flow interview. No configuration on your part is needed.

Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.

Who: By default, the Sample Flow Report: Screen Flows report is visible for all users. However, each user can only see information for the flows for which they're the running user. The report uses data from the new Flow Interview Logs and Flow Interview Log Entries primary objects. By default, only users with the View All Data permission can see other users’ flow log data. To give users the ability to view information about flows run by other users, set up sharing settings for the Flow Interview Logs object. To restrict view access to the report, move it to a different folder.

Why: We heard your feedback that you want a more efficient and time-saving way to find out runtime details about the flows you build. Now you can use the new Screen Flows custom report to discover information about your screen flows. For example, you can see who’s running a flow you created, and get a better understanding of its adoption. And service managers can see how fast their teams complete their tasks with flows versus without. These metrics provide insights about whether the business could benefit from more process automation or less.

Salesforce automatically adds the Screen Flows custom report type and report to orgs that haven’t reached their org limit for the number of custom report types. Orgs that already have a custom report type with the same API name as the Screen Flows custom report type ("screen_flows_prebuilt_crt") do not receive the Screen Flows custom report type. Orgs that already have a report with the same report type name ("flow_screen_prebuilt_report") do not receive the Sample Flow Report: Screen Flows report. If your org doesn’t receive the report, you can create a custom report type using the Flow Interview Logs and Flow Interview Log Entries objects. Users then can create custom reports using the custom report type.

The Flow Interview Log Entries object generates a log record for each screen flow that’s active in the last 31 days. The limit for the Flow Interview Log Entries object is 7 million log records a month, for the previous 31 days. Orgs rarely reach this limit. But when the limit is reached, Salesforce stops logging metrics for new flows. After 7 million records in 31 days, no new flow executions are counted. However, if a flow interview is in progress when this limit is reached, Salesforce continues to track metrics for the flow interview. Salesforce automatically deletes all logs that are older than 31 days, even for orgs that haven’t reached the 7 million-records limit.

How: From the App Launcher, enter report, click Reports, and then Public Folders. Find and select Sample Flow Report: Screen Flow. If you don’t see the report, that means we couldn’t automatically add it. Either your org is at its maximum custom report type limit or your org already has a report with the same report type name.

The new "Sample Flow Report: Screen Flows" report

The report displays flow interviews that ran within a specified date range for the Flow Interview Logs and Flow Interview Log Entries objects. By default, the results are sorted by flow API name and interview status. The results include the total time and the average time that users spent on a flow screen, and the number of flow interview log records generated for a flow within the reporting period. To change how the report is sorted or to report on different fields, edit the report.

The default date range is the last 7 days. If you don’t see all of your flows, change the date filter to a wider range. The maximum range is the last 31 days.

Remember that the data in the report is for screen flows only. The report includes data for screen flows that users started, paused, and finished, and screen flows in which users clicked Next. Autolaunched flows and flows that don’t require user interaction are not logged.

Typically, reports measure completed work. However, the Screen Flows report tracks active flows that are still in progress, in addition to completed flows.