Cloud Flow Best Practices

For Power Automate developer, here you can find several best practices to make your cloud flows easily maintainable.

• All flows should be managed with one admin user.
• Avoid using “My flows” area while working with Customer Engagement projects. This will cause a Connection issue for the future. Flows needs to be created from Solution. It must be solution-aware flow. Non-Solution-aware flows uses “Connections” instead of “Connection Reference”.
• There is no general view for Solution-aware flow. Make sure that all flows are managed into one solutions.
• There should be configuration entity to keep all static informations which is used in cloud flows. If there is more than one static, the items should be stored as json format. JSON can be parsed easily in cloud flow.
• Only existing Connection References should be used. If any Connection Reference has reach out the limit (16) new connection reference needs to be created.
• Connection Reference naming convention should be like (ReferenceName_IncrementNumber). Make sure that the latest number are used in newly created flows. (Eg: Dataverse_1)
• Flow Description field will be filed with implemented logic. And Configuration values which is used in flow needs to shown in description area.
• All cloud flows should have a Try-Catch approach which is described below. All possible errors should be visible in any place. (See this Article)
• There should be one more additional flow which checks all Turned off flows. Sometimes cloud flows are turning off itself because of unexpected behaviours. Make sure that we are aware of any turned off flows.