What it requires. A flow should stay within a workable size. Beyond any of these, logic belongs in subflows: more than 50 elements; cognitive complexity above 15, where each loop or decision counts one and each level of nesting adds a further penalty; cyclomatic complexity above 25, counting loops and decision branches; or any loop nested inside another loop.
Why it matters. Three separate Salesforce sources name the monolithic flow as an anti-pattern: consolidating an object's automation into one mega-flow brings no performance benefit while making refactoring, debugging, and onboarding harder. Nested loops also multiply executed elements per interview, which walks towards the runtime interview limit.
How to fix it. Extract the nested or repeated logic into subflows, each with a single responsibility. Where the complexity is inherent rather than accidental, record why in the flow description so the next person does not mistake it for neglect.
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.