Flow Failure Notifications (Power Automate)

Get email alerts with direct links to the flow run any time your flow fails by adding this set of actions to the end of your flow.
Template & Community Thread: powerusers.mic...
Microsoft started renovating their community site. They didn't transfer the download files from the old site, & I can't manually re-upload any of the download files there at the moment. I'm waiting on a solution from their support team.
In the meantime, here is a Google drive link to a zip folder with solution imports for most of my projects: drive.google.c...
Reza Dorrani Video on Flow Run Links: • Power Automate flow Ex...
Power Automate Expressions Guide: docs.microsoft...
Venmo
venmo.com/u/Ty...
PayPal
www.paypal.com...
Buy Me a Coffee
www.buymeacoff...
Thanks for any feedback,
And reach out on LinkedIn ( / kolota ) if you want to hire me to consult or build more custom Microsoft solutions for you.

[@victordauden9173]

Outstanding.It should be an official documentation template. Hats off to you sir

[@tylerkolota]

I submitted it as a template, so we’ll see 😊

[@JackDollarss]

Can I setup a Flow in Power Automate Cloud to notify me every time whenever there is an error in Power Automate Desktop? If so then how can I achieve this?

[@kanurikrvk974]

Hey, what you've created is awesome. Thank you. But just one question though, is this still going to work even If I have a giant power automate flow and use this flow at the end? cause from what I see you've composed all your action in one scope and I think my flow is divided into several if conditions in between and so on. Like for example action1->action 2->action 3 ->if condition and likewise

[@tylerkolota]

Yes. As long as it is placed at the end of the flow past any potential parallel branches and with the set run-after conditions then it will trigger when any preceding action in the flow fails & skips the actions between the failed action & the failure notification scope. If you want to test it you can put a Compose action in any of your branches & set an expression in it to div(1,0) to create a divide by 0 error on that branch & see what happens with the notification at the end of the flow.

[@kanurikrvk974]

@@tylerkolota I appreciate you giving the reply. can't wait to try this out. cheers!!

[@MarcWinter]

@@tylerkolota Many thanks for pointing this out! I was under the assumption that "run after" refers to the directly previous step. (The interface suggests so: it shows the previous step left to the checkboxes for is successful, has failed etc.) Nonetheless, it works as you said. One addition, though: this does not work when you're testing a flow via "Test" in the editor - in this case, it doesn't trigger the Error-Scope, but sticks to the location where the error really occurred. (This is perfectly ok, because you can debug it better then, but might irritate a bit when applying your solution)

[@tylerkolota]

@@MarcWinter Technically run after does refer to the directly previous action. It is just that in most cases if a preceding action in the flow fails then the last action before the failure notifications scope would be "skipped" & thus would trigger the failure notifications scope. But for example if you set the last action in the flow before the failure notification scope to run after its preceding action is failed or skipped then the failure notification scope would not run because the immediate preceding action was successful.

[@chikombechela2460]

Brilliant!! So helpful!

[@pavanireddy885]

So, does it mention which action failed in the email trigger so that I can go back and check that particular action?

[@tylerkolota]

To check what action failed you can click the link in the email which brings you to the failed flow run & the exact action that failed

[@AMindGame]

You're the Goat

[@rebeccax3880]

You are excellent. thank you!!

[@tylerkolota]

Thanks! I hope it’s really simple & useful for you.

[@rebeccax3880]

@@tylerkolota It took 5 minutes, very simple as I am newbie and have very little experience with flows and zero coding. I appreciate your expertise.

[@luupieper]

It works good, thank you for the tips, but I'm still struggling with the fact that, as the notification email runs successfully the flow is shown as successful in the flow runs list. Is there a way to have them appearing as failure (as they have, actually, failed)?

[@tylerkolota]

The last Terminate action should be set to mark the flow run as a failure. Did you also set the "Run after" settings to not run when the preceding actions are successful?

[@nadiaquinonez8085]

I followed but I get failed messages and I am not able to fix it.

[@tylerkolota]

You’re not able to fix what?

[@bryan4648]

My flow has failed, but im still getting failure notification. can anyone help?

[@tylerkolota]

Have you checked the “run after conditions” setting to make sure it is when failed, skipped, or timed out, but not on success?

[@abyal3kod201]

But I have like 10 actions in my flow, how do I do this?

[@tylerkolota]

If you put the scope at the end of the flow & set the run after settings the same way I do in the video, then it should work whenever any of those 10+ actions fail.

[@abyal3kod201]

@@tylerkolota So I should put all actions in my flow in one scope?

[@tylerkolota]

@@abyal3kod201 Not if you don't want to. If you just insert the Flow Failure Notifications scope at the bottom of any flow, & set the run-after to "On failure", "On skip", & "On Timeout", then it will trigger whenever any action preceding it fails and send the error notification. So if action 5 of 10 fails, then it's going to skip actions 6-10 and get to the Flow Failure Notification scope which will run when the previous 10th action is skipped and it will send the notification.

[@thalapanenirakesh8459]

So it works for multiple flows?

[@tylerkolota]

It works for almost any failed action (excluding Do until loop actions) within an individual flow. And it’s easy to copy & paste into several flows with a few clicks.

[@ScottKFraley]

Everything is only Set To Go if you've got the appropriate Connector(s) plugged in. Trying to figure it out now.

[@tylerkolota]

Sorry, what do you mean by “connectors plugged in”? Do you mean you don’t have an account resource created for each connector? In which case, either use the 3 dot ellipse on the side of the action to find the option to create a new account connection, or create a new action for each of the connectors in question & it should walk you through the steps automatically.