Sometimes there is no need for log everything professionally and monitor everything. But still Power Automate flows run history checking from the portal and finding failed flows could be time consuming work. When there are multiple developers there isn’t even possibility to get people developing the flow so that there are actions catching errors or sending error report to one place. But still there is need to get information when a flow fails – what to do?
Each environment offers Flow Run table which records each flow action and failure. It is quite easy to build a solution where is Power Automate flow checking the Flow Run table. When there is failed flow, it will notify administrators somehow – send email service desk, post a Teams message into maintenance channel or something else.
Then you need to install the solution in environments, where you want to have logging.
Please remember
- The flow needs to be in a solution to get logged into Flow Run table, luckily this month Cloud flows are automatically defined in Dataverse solutions | Microsoft Learn GA September 2024 – since before that “Currently, makers create non-solution cloud flows by default that aren’t stored in Dataverse. With this change, cloud flows are stored in Dataverse by default. We’ll provide an ability to migrate flows outside solutions to solutions, to simplify the administration process, and unlock new maker experiences.”
- Read the Microsoft documentation and limitations about the Flow Run table. It uses Dataverse capacity, so you might want to read above link and reduce records amount
This means that if you want to follow Default environment flow failures, you need to add all previously created flows all into one solution. You need to have Power Platform or Global Admin permissions, so that you get the admin permissions to the Default environment, to see each Power Automate flow created by citizen developers.
The solution to go around this is to install the free monitoring and governance tool CoE Starter Kit, developed by Microsoft and create your Power Automate follow only Cloud Flow Runs table rows and develop only one solution.