I'm running into a disturbing number of scenarios that prevent me from recommending Flow as a business solution for SharePoint
Most companies make people update passwords periodically. My understanding is that updating your password will cause Flows using the old password to stop working.
Flow also stops running if the Flow owner leaves the company and their credentials are deactivated. Even if they are shared as a team flow, the other owners will need to rebuild the Flow in order to take it over.
As the site owner, I have no way of knowing what Flows are running on my site, nor can I assist if there are problems.
Until Flow can be attached to the site, list or library and made independent of individual users the way a Designer flow is, I'm afraid i can't recommend it to my business as a viable solution. I can't risk having a global business process global used by thousands of users go dark every few months when I update my password.
I would love to move away from SharePoint Designer, but I can't until this is addressed.
This in turn also limits the functionality of PowerApps as many of the higher level functions are tied to Flow.