All docs pages (49)

Flow Hub

Check your active Salesforce flows for common anti-patterns and performance risks, read what each flow does, and see its versions.

Updated 2026-02-15

Flow Hub in SFDC Police

Flow Hub checks your org's active flows for common anti-patterns and performance risks before they cause problems in production. It is static analysis: it reads each flow's metadata and does not run the flow.

Features

Flow List

Flow Hub lists your org's active flows (up to 200, sorted by name; search by name to find others). Each row shows:

  • The flow's name, with a link to open it in Salesforce
  • Flow type (Screen, Auto-Launched, and so on). Salesforce stores record-triggered and schedule-triggered flows as auto-launched, so they show as Auto-Launched.
  • A dot coloured by risk level (hover it to read the level), and the flow's test coverage when Salesforce has it

You can select flows and deactivate them; Flow Hub asks you to confirm first.

Flow Details

Open a flow to see four tabs:

  • Overview — a step-by-step text summary of what the flow does
  • Health — the findings from the checks below
  • Risk — the trigger type and object, a risk level, and how many elements of each kind (decisions, creates, updates, deletes, actions, screens) the flow has
  • Versions — the flow's versions

The Risk tab of a screen flow in Flow Hub, showing trigger, risk level, flow elements and subflow dependencies

1 The Risk tab. 2 Trigger type and trigger object (dashes for this flow). 3 Risk level. 4 Flow elements. 5 Subflow dependencies. 6 Open in Salesforce.

Checks

Flow Hub checks each flow for:

Performance

  • SOQL queries inside loops
  • DML operations inside loops
  • Record-triggered flows with many DML or query elements (more than 5 in total)
  • Too many elements (more than 50)

Anti-patterns

  • Hardcoded record IDs
  • Unused variables
  • More than 8 decision elements in one flow
  • Updates to the object that triggers the flow (risk of re-triggering)
  • Triggered flows with no entry conditions
  • IsChanged() in a scheduled path, where it does not work
  • A missing flow description

Reliability

  • Data operations and actions with no fault path
  • Get Records results that may not be checked for null (flagged when a Get Records element has no fault path)

Screen flows

  • Delete elements in a screen flow

Issue Severity

Each finding is grouped as:

  • Errors — likely to cause errors or data problems
  • Warnings — may cause problems under some conditions
  • Info — a best-practice suggestion

Interpreting Results

Not every finding needs immediate action. Use the groups as a guide:

  • Fix Errors before release
  • Review Warnings and decide based on context
  • Info items are improvements, not blockers