cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
BLawless
Frequent Visitor

On Error Block not triggering and catching error, resulting in flow failing

Hey guys, y'all were pretty helpful with a deeper concept I was trying to wrap my head around, so it's time for a softball (because I'm pretty sure the issue is located between the keyboard and the computer chair).

I've been trying to implement "On Block Error" blocks that will catch any errors thrown by the actions they are encapsulating and handle them so the main flow doesn't fail. Every attempt at this however has failed to catch any errors thrown by the actions the block encapsulates, this is both when I just have actions as well as when I have calls to sub flows that are contained within an "On block error" action. 

To help visualize my issue (see pictures below) I created a very basic "example" flow that creates an array of a certain length and, inside of an "On block error" action, it will attempt to assign a a value to an index that is out of bounds for the array (and should therefore throw an IndexOutOfBoundsException upon attempting that action).

I have not set individual error handling actions (namely because "Set varaible" does not have any "on error" properties), but this is applicable to actions that also have individual error handling properties. Every time the flow attempts the action it will cause the whole flow to fail with a runtime error of the index being invalid. The "On Block Error" is not set to throw an error in response to catching one, so the error causing the flow to fail (from my observations) is the one thrown by the action inside of the "On block error" block. It is worth noting that I in the example I am calling this sub-flow from the Main flow, which has the sub-flow call encapsulated in another "On block error" action, which means two different "On block error" actions have failed to catch and handle this error.

I have tried setting it to "Continue flow run" and either "go to the end of block", "run sub-flow", "go to beginning of block", etc. None of these actions take place, it simply behaves as if it didn't catch the error and the error made its way unhandled to the main flow runtime level and caused the flow to fail. 

I'm hoping this is just a simple configuration issue but if there are limitations to the "On block error" action that I am not aware of then I will happily expand on other scenarios where I am implementing this action (because none of my attempts with "On block error" have been successful thus far). 
Error thrown from the previous run at the bottom reports that the flow was stopped because of the action performedError thrown from the previous run at the bottom reports that the flow was stopped because of the action performed"On Error Block" configuration"On Error Block" configuration


2 ACCEPTED SOLUTIONS

Accepted Solutions
yoko2020
Responsive Resident
Responsive Resident

@BLawless 

I agree with your statement, applying individual exception in every action is ridiculous approach if we have complex flow.

 

But this is the reality, there are some action/error which did not get captured by On Block error. It still does not work as we expected same as like we apply Try Catch Exception in C#/Vb.Net.

View solution in original post

Rkv_
Resolver II
Resolver II

Hello Everyone, 

The Onblock error can only able to capture the failures happened with the actions which contain on error property and the errors listed with in the advanced tab of the on error.

 

For example the below action Get window contains On error.

 

Rkv__1-1630316620306.png    

Rkv__2-1630316661006.png

So the Onblock error able to capture if this action failed to get window.

The below action is the IF condition, which don't have on error, and this cannot be captured in Onblock error.

Rkv__3-1630316786825.png

 

 

 



View solution in original post

8 REPLIES 8
Henrik_M
Super User
Super User

Power Automate Desktop cannot handle IndexOutOfBounds exceptions 👎

 

If you are not 100% sure that the index will be valid during execution, you will have to do a manual check (using %List.Count%) instead of relying on the block error...

If the "On Block Error" doesn't catch errors like IndexOutOfBounds Exceptions then what errors are they capable of catching? Is there a reference list somewhere? 

 

I do agree with you that there are means to verify whether or not something should cause an error before performing the action (and make the actions performance conditional to that verification), but with complex flows there's a lot of edge cases that would be better off handled by a simple "On Block Error" segment. In my experience, individually checking all these cases for an error triggers would severely impact the readability and debug performance of the flow. 

yoko2020
Responsive Resident
Responsive Resident

@BLawless 

I agree with your statement, applying individual exception in every action is ridiculous approach if we have complex flow.

 

But this is the reality, there are some action/error which did not get captured by On Block error. It still does not work as we expected same as like we apply Try Catch Exception in C#/Vb.Net.


@yoko2020 wrote:

But this is the reality, there are some action/error which did not get captured by On Block error. It still does not work as we expected same as like we apply Try Catch Exception in C#/Vb.Net.




Marking this as the solution since it touches directly on the general issue, which is that the "On Block Error" doesn't capture every exception the same way a Try-Catch block does in other contexts.

From what I've gathered here it seems that the only errors that the "On Block Error" catches are those listed under the "advanced" segment of the actions "on error" actions. If this is true then actions such as assigning variables are capable of throwing errors that the "On Block Error" cannot handle. This is unverified but makes the most sense based on the discussion here and my observations. 

yoko2020
Responsive Resident
Responsive Resident

Here is just sample, and there are many more i can not remember.

This error did not catch by the On Block error.

 

That means if you have internal subflow function for handling global exception, it will not be executed.

(EX: if %GeneralException% = 1 then take a screenshot of desktop and send it via email )

 

Spoiler
2021-08-29_084245.png
Rkv_
Resolver II
Resolver II

Hello Everyone, 

The Onblock error can only able to capture the failures happened with the actions which contain on error property and the errors listed with in the advanced tab of the on error.

 

For example the below action Get window contains On error.

 

Rkv__1-1630316620306.png    

Rkv__2-1630316661006.png

So the Onblock error able to capture if this action failed to get window.

The below action is the IF condition, which don't have on error, and this cannot be captured in Onblock error.

Rkv__3-1630316786825.png

 

 

 



BLawless
Frequent Visitor


@Rkv_ wrote:

Hello Everyone, 

The Onblock error can only able to capture the failures happened with the actions which contain on error property and the errors listed with in the advanced tab of the on error.




Thank you @Rkv_  for confirming my theory posted in my last comment (here). Going to update the post to represent your comment as the solution as it points out the core issue. 

The previously marked solution by @yoko2020 is still input valuable as it touches on the core of how PAD under the hood isn't a programming/scripting language but features script-like operations to allow non-programmers to use the automation without having to learn a full programming language and has some limitations as a result (which we may be able to mitigate, see followup further down). 


@yoko2020 wrote:

But this is the reality, there are some action/error which did not get captured by On Block error. It still does not work as we expected same as like we apply Try Catch Exception in C#/Vb.Net.



Furthermore thank you for your example contribution (found here). 

 


As a followup:

I think there is a workaround but it may take some time to verify.

It might be possible (in cases where doing checks for validation on all edge cases is impossible with other actions) to perform the analog equivalent of the PAD action inside of a "Run JavaScript" action and use a try-catch block there (the one under "System", not "Run JavaScript on webpage unless you're using a browser to perform actions on a page). Knowing how variables work between the translation layer of a "Run JavaScript" action and the variable assignment in the flow, this will not work for every scenario, but I think a combination of this and using validation checks using other actions in PAD will cover most (if not all) of advanced edge cases. 

If JavaScript isn't your thing, "Run Python script", "Run VBScript", "Run PowerShell script", and any other "Run [Insert Programming Language here] Script" that Microsoft implements into PAD in the future (C#?) are good alternatives. 

I know for non-programmers this may not be ideal, but if you're running into scenarios where you need the full function of a try-catch block, chances are you're at the level to learn enough about one of these languages to do a try-catch block and scripting analog of whatever action you're wanting to perform in PAD. 

Anonymous
Not applicable

💩This is pain in butt. Try-Catch construction that cannot be trusted is a nightmare. It makes it really difficult to explain to customers why the robot terminated without sending any email warning as it should by the process design...  💩

Helpful resources

Announcements

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (5,231)