Salesforce Flows are where most automation lives, and unlike Apex there is no compiler to tell you which ones still matter. The Flows section answers that from two directions: what exists, and what actually ran.
It sits beside Apex in the graph's section switcher.
Like Apex, Flows has two scopes and the same switch between them.
Backbone shows only the flows that trigger on the objects your processes are built on — the ones in your graph. This is the view to use when you are reviewing a process.
Org-wide shows every active flow in the org, whether or not it touches your backbone. This is the view for an estate review: it is usually the first time anyone sees the whole set in one place.
Each flow is scored by its step count — how many elements the flow contains. It is a proxy for complexity, not a judgement: a 60-step flow is not necessarily wrong, but it is certainly harder to change than a 6-step one, and it should be a deliberate choice rather than an accident.
Flows are grouped by the object that triggers them, so you can see at a glance that one object carries eleven flows while another carries none.
Structure alone cannot tell you whether a flow earns its keep. If the analysis has Event Log data for the period, each flow also shows:
how many times it ran
how long it took
how often it errored
This is where the useful surprises are. A flow with a high step count and no executions is pure maintenance cost. A flow that errors on a tenth of its runs is a live problem that nobody has reported.
Flows that are active and deployed but never executed in the analysed window are listed separately. They are the natural first candidates for removal — but read the window before acting. A flow that only runs at quarter end will look cold in a two-week window.
Salesforce does not store Process Builder processes as their own metadata type. They are stored as flows, and they arrive in these tables looking like any other autolaunched flow.
Stood Flows identifies them and marks them with a red tag. Red because it means retired: Salesforce stopped allowing new ones in Spring '25 and ended support on 31 December 2025. They still run, but they receive no fixes — so every one of them is a migration candidate.
One value is worth knowing about. Salesforce labels the record-change variety Workflow, which reads like a workflow rule. It is not — workflow rules are a different metadata type that this analysis does not cover. The detail panel spells it out as Workflow (Process Builder) so the two cannot be confused.
Flows is refreshed by two analyses in a full run: Flows org-wide rebuilds the structure, and Visits (ELF)'s sibling, Flows usage (ELF), adds the runtime numbers over the period you choose. You can run either on its own if you only need one half updated.