When creating actions we should have a flow element that provides a visual hint of other flow elements that are directly related to the same logic, in order to allow easier code understanding by visually breaking it into concepts in scenarios where breaking the code into several actions isn't desired. 

A named box around the elements would would do nicely.

Support of folders within folders and an optional set of action meta data properties that generated variations of the default icon representation would also be possible ways to implement this as well.

Best practice commands not using the "Z" type of coding but some of my colleagues do it anyway "to group common statements" to highlight a specific branch of actions. 

In other software in the past (mostly MySQL DB designers and Talend Open Studio), there was a functionality to enclose these elements in individual groups by drawing a rectangle area (region) on the canvas around those statements/elements, thus clearly highlighting different branches or actions...

Much like C# has the #region marker, I thought it could be added as a component.

There is this widespread idea that flows should not be large, and if they get too large, part should be split off into a separate action.  In that spirit, there is less need for defining sections in an action flow.  I suspect there is also the fear that introducing sections will remove the trigger for splitting your code up in smaller parts.

I myself sometimes am reluctant to split off stuff that clearly belongs together.  One of the things I have used is to put a Comment behind it, and making it large enough with spaces en newlines.  But that is really a hobbyish makeshift workaround, since the comment has no relation to the widgets it represents, so you can't for example move the section and drag all that is in it, with it, you are forever adding or removing spaces and newlines while your logic develops, because you can't just resize it, etc...

If we had a section widget, we could also collapse/expand sections.