Why this Flow should be code

Not every Flow should become Apex — most should not. This lesson is about recognising the minority that should, before it costs you a weekend.

The three signs

You are scrolling. A Flow that no longer fits on one screen has stopped being a diagram. The whole argument for the canvas is that you can see the logic; once you are panning around it, you have the downsides of code with none of the tooling.

You built a loop inside a loop. Nested loops in Flow are where interview counts and element limits go to die, and the canvas gives you no way to see the cost. Code makes the cost legible — which is the point of the next seven lessons.

You are copying element groups. The fourth time you duplicate the same five elements and change one value, you have discovered why functions exist, in the one tool that does not have them.

The two signs it has not

It fires rarely, and an admin who is not you needs to change it monthly. An automation the team has to own belongs in the tool the team can read — which cuts both ways, and later in this course we will move one automation back to Flow for exactly that reason.