It seems that there are a number of things that can go wrong that will cause a flow to fail, and I don't think I have seen a reliable reporting of failed flows. If we create a flow to automate a process, the assumption is that we don't have to continue to actively monitor the process to know that it is working.
Are there some best practices to ensure errors are handled the best way and reported when they occur?
It depends how crutial the failures are for the business. You can add an action after a failure explicitly adding the action to every flow step. It's similar like in programming programmer decides which exception need to handled internally and carry on or throw an exception, log the details / notify.
For flow you can set against configure run after option to decide what to do with the exception.
Please have a look at this link.
Also there is a generic notification via email you can receive. Have a look at this.
I have started looking into this. I haven't gotten very far. This assumes I can anticipate where the failures will occur. If the problem is in the trigger, I'm sunk.
There ought to be a way to have a global handler that will execute for any unhandled exception.
Thanks for your reply. If you think trigger failures and global exceptions need to be handled you can post this in the idea forum.
Check out new user group experience and if you are a leader please create your group
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.
Many congratulations to the Season 1 2021 Flownaut Crew!
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.