Error Handling in Power Automate flows | Try Catch Scope Action

In this Power Automate video, we will look at how to perform exception handling in cloud flows leveraging configure run after setting, using scopes as try & catch exception handling blocks, sending notifications for failed flows, specifying which actions failed or time out and the reason for the failure. We will also provide a link back to the flow run for the failed Power Automate flow instance.
Getting notifications when your flow has failed because of an error is critical to maintaining business continuity. Also, the notification should provide the cause of the error to help you resolve it quickly. This video will focus on how you can use Configure run after, an option that is available for flow actions, to help isolate errors.
The Configure run after option and email notification is beneficial in helping you swiftly resolve issues with your workflow run.
Use the Configure run after option to handle errors: You can identify which step failed and, if it did, bring that to your attention. You can get the error description, status, action etc. by using expressions like result & actions.

Power Automate Exception Handling video includes:
✅ Standard flow failure notifications and analytics
✅ Configure Run after setting to notify errors - Has Failed, Timed Out etc.
✅ Terminate action to set flow status as failed
✅ Using scopes to group actions together and handle errors - Try, Catch, Finally Scopes.
✅ Handle flow errors inside apply to each loop.
✅ Power Automate error handling flow template

Helpful Links 🔗

Best practices for error handling in Power Automate flows:

Download Error Handling Power Automate flow Template ⬇️

Expressions used in video ⚡

Power Automate flow run URL:

Filter Query Expression to check if Try Scope action has Failed or TimedOut:
@or(equals(item()?['Status'], 'Failed'),equals(item()?['Status'], 'TimedOut'))

Table Style 🖌️ (Included in template)

#PowerAutomate #ErrorHandling #flow

Table of Contents:
00:00 - Introduction to Error Handling in Power Automate Cloud Flows
00:36 - Flow Failed! How to check for errors?
02:05 - Power Automate Error Handling - Send Instant Failure Notification
02:58 - Configure Run After in flows
03:28 - Get flow failure error message using outputs() expression
04:46 - Terminate action in flow
05:23 - Get Power Automate flow run link using workflow() expression
06:28 - Multiple flow actions error handling using Try Catch Finally Scope blocks
12:01 - Error Handling Power Automate flow Template
13:24 - Flow apply to each loop error handling
17:13 - Subscribe to Reza Dorrani channel

🤝 Let’s connect on social:

[AnandhAdhithan]

More useful for citizen developers. Thanks for the video. Excellent explanations!!!

[Amritasthegreatindiantaste]

As a beginner , You helped me lot to learn Power Platforms . Thanks for such detailed videos .🤗

[ankushjain]

There are many times I have used the try catch block in a flow in the past but still this topic holds something new for me to learn.. Thanks Reza for updating all these scenarios in such a beautiful manner. Keep it up, you are doing an incredible job.

[antoniobranderas]

So I had this situation today. My flow failed trying to send a simple email. Something was going on with our power platform today. From what I can tell there is no way to catch an error with an email notification if notifications are the cause of the failure. PS: GREAT VIDEO!

[keithdavies]

Hi Reza, very informative video and clear instructions on handling errors. Unfortunately, one of my mailbox handling flows failed with a connection error, which rendered the options to send email or Teams message, or to add an entry to a SharePoint table all inoperable.
What would you recommend for connection issue error trapping?

[Jaxkookie]

Hey Reza, this some great work you are doing. I am playing with the try catch scope. I have nested conditions and if a nested condition fails, the error message reflects the top parent, not the nested action. How do I get the nested action error message?

[jt]

Thank you, again, Reza! You have so many useful videos, with lots of tips and tricks. I find them so useful for my work! Many Thanks!!!

[Nomadicne]

Thank you for this solution! As usual, explained clearly and professionally.

I do have a question though:
I am creating (or updating) an item in SharePoint Online via my flow. Occasionally it fails due to one of the item properties being incorrect (such as the user in a People field not being found).

Is there a way to catch the error and return which propety exactly was the point of failure?
(I'd like to report the property and possibly try updating again in the catch block with that property excluded.)

[generice]

Hi Reza, great video, I finally got around to creating my own Error Handling Template for my department to use. One question, in the last segment, where you handle the Apply to each and the array created from an error in the Create item action. How can I incorporate that functionality into the previous segment's Try/Catch solution? Does every Apply to each scenario need its own check?

[dankirchner]

Thanks Reza! Great as always sir. I have a quick question. Is there a way to throw an error message to the user in power apps if a flow doesn't run?
I'm just thinking of a flow doesn't run then the user could just be sitting there waiting and not knowing there's an error and the error has been reported to the developer.
Appreciate any help you can give on this idea!

[vkrish]

I am a regular visitor of Reza's videos and as usual his signature top class is visible. Great work Reza!

[mevankattan]

Thank you for this great video! Sorry if I've missed this (Ive watched the whole video) but how do you handle errors if you have an Apply to Each loop but there are a lot of actions inside (multiple conditions/actions etc). How can I handle this?

[mohammedmerchant]

Hi Reza, this tutorial was very helpful in making any Flow more robust. I'd like to know if a Flow is triggered from Power Apps, how can I import your template to start using it? For my Flow through the App, I recreated the steps you outlined but doing that each time isn't viable, so I was wondering how to go about using the template through Power Apps?

[finalfant]

Thank you. I was on the right track with the Scope thing, but I was sticking it in a parallel within the apply to each loop so my flow was still failing. Basically, I know that my flow was going to fail on several and I didn't really care to know that it failed, so I just wanted the ones that failed to drop off and be ignored without failing the flow. I just added a scope that ran after apply to each failed and then terminated with a successful message. I know this isn't ideal, but I am dealing with a condition that isn't evaluting correctly which is supposed to drop the items that are failing anyway. Until I get that bit figured out, this is a good band aide to allow the flow to run as "normal".

[pauljhongacutan]

Excelent video and easy to understand the explanations. Quick question though, we know that the "Result" expression only gets the top level actions. Do you know any ways to get the error details from the succeeding levels or from the actions like (If Statement, Switch or within a nested Scope)?

[StephanOnisick]

So Awesome. that I had to watch 5 times and take Screenshots to begin to understand. I will definitely have to incorporate this.

[ericzheng]

Pretty much same as the previous error handling from another video from you. But this time it is very clever to add a termination with 'Fali' in the end so the status remains as it should be. Geniues Reza!

[tracyqian]

Hi Reza, thanks a lot for your video as always! May I know how to do the error handling if I have many steps in Apply to each? How can I catch the error message for each step? Thanks in advance.

[yojanhernandez]

Great job!
Very good explanation, organization and also dividing the video by chapters, was a great help, thank you very much!

[naveenkarla]

Awesome Video Thanks Reza!. Do you recommend retry policy for any specific error types. Also i believe result function goes only one level deep. Thank you