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

Win free tickets to the Power Platform Conference | Summer of Solutions

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏 Markus Franz | LinkedIn  Power Apps: mmbr1606  

Copilot Cookbook Challenge | Week 1 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery:  https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the challenge.   Week 1 Results:  Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

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.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Reminder: To register for the Community Ambassador Call on June 13th

Calling all Super Users & User Group Leaders   Reminder: To register for the Community Ambassador Call on June 13th—for an exclusive event for User Group Leaders and Super Users! This month is packed with exciting updates and activities within our community.   What's Happening: Community Updates: We'll share the latest developments and what's new in our vibrant community.Special Guest Speaker: Get ready for an insightful talk and live demo of Microsoft Copilot Studio templates by our special guest.Regular Updates: Stay informed with our routine updates for User Groups and Super Users.Community Insights: We'll provide general information about ongoing and upcoming community initiatives. Don't Miss Out: Register Now: Choose the session that fits your schedule best.Check your private messages or Super User Forum for registration links. We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Users online (2,469)