How to scope variables in a specific subflow so that it cannot be accessed accidently or intentionally in other subflows?
In the Power Automate desktop, the Flow variables pane becomes too much cluttered as soon as the program becomes complex. It becomes too much difficult to see the specific variables created in one subflow to use them in the same subflow.
So what about the concept of scoping variables (in PAD) between local and global level to cater the complex programming tasks?
