cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
olgaoszcz
Advocate V
Advocate V

Get error message for the action 'on failure'

Hi, 

I'm trying to set up error handling in one of my flows. I have 'Create file' action and then 'Exacute strored procedure' on failure. First issue i noticed is if my 'create file' failes but the stored procedure is executed, in the run history it still says Flow was succesfull. I don't think thats informative enought - something still failed and it should be visible in the run history.

failed but successfull.png

You can't just say it run successfully, when one of the steps failed...

Second issue I have is that I have the information on which step of my flows failed but I would also like to get the error message flow provides.

errormsg.png

It would make life so much easier to have the error message avaliable as a dynamic content... Does anyone had a similar problem? Any ideas on how to work around it?

 

2 ACCEPTED SOLUTIONS

Accepted Solutions
yashag2255
Super User
Super User

Hi @olgaoszcz 

 

The action "Create File Failure Event" you have modified the run after settings of this action to run even when the Creaet File Action fails (please click the ... on the action to see the run after settings) and therefore flow carries on the process instead of marking failed because it is being made to move to the next action forcefully when the particular action has failed (makes sense?)

 

The get error message as dynamic content is currently unavailable as a direct action in flow. You can post that as an idea here:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

Hope this Helps!

 

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

 

View solution in original post

MichelH
Advocate V
Advocate V

Hi 

olgaoszcz

 

 

I have been trying to obtain the same thing, just simply getting the error message in flow, and sending it to myself.

 

I found it can be done using the actions() function.

In your case the argument of the action function would be 'Create_file' since that is the name of the component you want to monitor.

It will return an object somewhat like this example of: actions('Set_variable_3')

{
  "name": "Set_variable_3",
  "startTime": "2019-09-09T19:46:51.4123218Z",
  "endTime": "2019-09-09T19:46:51.4123218Z",
  "trackingId": "53a0681f-7810-4bbe-9494-a5cdcdeadb0b",
  "clientTrackingId": "08586335800123686594686241510CU42",
  "clientKeywords": [
    "testFlow"
  ],
  "code": "BadRequest",
  "status": "Failed",
  "error": {
    "code": "InvalidTemplate",
    "message": "Unable to process template language expressions in action 'Set_variable_3' inputs at line '1' and column '2677': 'The template language expression 'actions('conversion_to_currency').outputs.body.status' cannot be evaluated because property 'status' doesn't exist, available properties are 'name, value'. Please see https://aka.ms/logicexpressions for usage details.'."
  }
}

So in my case the name of the component I monitored was 'Set_variable_3' .

 

Now in order for you to get just the error message you can say: actions('Create_file').error.message

If you want to check first if the action failed or succeeded you can check the status: actions('Create_file').status

 

You can use these as arguments in the SQL 'Create_Failure_Event' component to store the error message if any.

Or you use these to fire a terminate component that matches the status

 

Best regards,

 

Michel

 

View solution in original post

31 REPLIES 31
yashag2255
Super User
Super User

Hi @olgaoszcz 

 

The action "Create File Failure Event" you have modified the run after settings of this action to run even when the Creaet File Action fails (please click the ... on the action to see the run after settings) and therefore flow carries on the process instead of marking failed because it is being made to move to the next action forcefully when the particular action has failed (makes sense?)

 

The get error message as dynamic content is currently unavailable as a direct action in flow. You can post that as an idea here:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

Hope this Helps!

 

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

 

Hi @yashag2255,

Thank you for your message.

I set up the 'on failure' on purpose only after the create file fails to handle the errors. As i understand thats what it was developed for...  https://flow.microsoft.com/en-us/blog/error-handling/

Therfore I do not understand why the flow 'is successfull' when it clearly isnt, only the erros have been handled successfully...

Pstork1
Multi Super User
Multi Super User

Consider putting a Terminate action after the Create File Failure Event and set the status to Failed.  That will let you specify an error code and an error message where you can pass on the error message that you have inside the Flow. That Terminate will only run if the Create File Failure Event runs because the create file failed.  The Terminate command will End the Flow at that point (its the end anyway), mark it as failed, and the errror message will be available in the Flow Run record.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

@olgaoszcz 

 

Yes! On the blog you can see that the error handling was configured to check and introduce a way that if a particular action is successful move and perform an action and if it is not successful (Timed out, Skipped, Failed) then do a particular action. So once you force the flow to perform actionsbased on the previous ones, the logic is built that we have intentionally added the action and we want to log it that way (example: if the action was successful go and update an item on SP and if it failed then log an error to another list or send an email to someone and then configure a retry and things like that). 

 

As @Pstork1 mentions, you can use the terminate action to generate an error code and show the status if something has failed but you cannot use the output of that elsewhere as the flow terminates at that action. 

 

Hope this helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Hi @Pstork1 ,

The Terminate action sounds like a good solution but the Create File Failure Event is not the end of the Flow, it's actually inside the 'apply to each' and I want the Flow to run through the other files even if one of them failed. Also, I want to have the error message as a dynamic content to send it together with the error alert. 

Thanks for your help Smiley Happy

 

Add an action inside the loop right after the action that can fail.  Set the new action to only run if the previous action failed using 'Configure run after'. The new action should set an error message which you can return at the end of the program.  If the previous action succeeds then the error action will be skipped. Make sure to set the other actions after the error action to run if the previous action was successful or skipped.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Thank you @Pstork1, as you can see from my post, that is exactly what I have done in my Flow. Although, this doesn't allow me to pass the error messages to the next action, there is no possibility to get the error message as dynamic content to pass it thought. This functionality doesnt exist and I'm planning to post that in Flow Ideas.

Thanks for you input.

@olgaoszcz 

 

As mentioned in one of the previous posts, the error message action genearted when an action fails cannot be passed further in the flow right now. It is a good idea to go ahead and create that as an idea on the community forum. 

 

P.S. For some reason this has been happening with me, I am trying to reply to a conversation and then suddenly the accept solution button gets clicked so please excuse me for that. Just trying not to do that (happened on a couple other threads too so my apologies)

 

Can you please mark this thread as answered to the appropraite post(S) that helped you!  Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search.

MichelH
Advocate V
Advocate V

Hi 

olgaoszcz

 

 

I have been trying to obtain the same thing, just simply getting the error message in flow, and sending it to myself.

 

I found it can be done using the actions() function.

In your case the argument of the action function would be 'Create_file' since that is the name of the component you want to monitor.

It will return an object somewhat like this example of: actions('Set_variable_3')

{
  "name": "Set_variable_3",
  "startTime": "2019-09-09T19:46:51.4123218Z",
  "endTime": "2019-09-09T19:46:51.4123218Z",
  "trackingId": "53a0681f-7810-4bbe-9494-a5cdcdeadb0b",
  "clientTrackingId": "08586335800123686594686241510CU42",
  "clientKeywords": [
    "testFlow"
  ],
  "code": "BadRequest",
  "status": "Failed",
  "error": {
    "code": "InvalidTemplate",
    "message": "Unable to process template language expressions in action 'Set_variable_3' inputs at line '1' and column '2677': 'The template language expression 'actions('conversion_to_currency').outputs.body.status' cannot be evaluated because property 'status' doesn't exist, available properties are 'name, value'. Please see https://aka.ms/logicexpressions for usage details.'."
  }
}

So in my case the name of the component I monitored was 'Set_variable_3' .

 

Now in order for you to get just the error message you can say: actions('Create_file').error.message

If you want to check first if the action failed or succeeded you can check the status: actions('Create_file').status

 

You can use these as arguments in the SQL 'Create_Failure_Event' component to store the error message if any.

Or you use these to fire a terminate component that matches the status

 

Best regards,

 

Michel

 

What I was suggesting is that you create a variable.  Then when the action fails set an error message in the variable as the action that runs after failure.  That would preserve the error for the rest of the Flow.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

You can put the result in a variable ofcourse, but I believe the resulting object of action('component_name') will remain available throughout the flow anyway.

 

The action formatting you mention should be there.  The problem is that the question said this was being processed in a loop.  That makes it tough to get back to the specific action that threw the error.  In this case I normally toss the messages into an array so I have all the error messages later.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Ah OK, bad reading on my part.

I saw the sql statement and thought status was to be written into a DB.

 

 

Hi @MichelH and @Pstork1 ,

 

Thank you @MichelH , that was exactly what I was looking for. The error message is supposed to be entered inside the SQL statement and stored in the database. That makes it easier for me to control the flow reliability. Thank you for your help Smiley Very Happy

 

@Pstork1 - You proposed to insert 'Temrinate' action inside the loop which I cannot do after the 'Create a file' because that will stop the flow immediately while I still want it to be able to loop through the other objects and continue the Flow after the loop. I need the error message only inside the loop. I have another 'on failure' later in the flow to pass errors from future actions. But thatnk you for your help and feedback.

Atima
Employee
Employee

"outputs('<action_name>')" function (in "expressions" of dynamic content) can be used to capture the output of the specified action. This can capture the errors as well but only if they are generated as output by flow at runtime. So a new step that is configured to run after an action fails can use this function to capture the dynamic error message.

Error as outputError as output

Murderbot
Advocate IV
Advocate IV

It looks like MS has changed the error reporting method recently and I am able to pull the detailed error message from an action with

body('<action name>')['errors']

. Unfortunately, I haven't figured out a way to make this statement dynamic - you have to reference a particular action (can't use variables or nested statements).

If you embed the action in a scope you can use 

 

result('scopename') 

 

to get the full error messages from the action inside the scope that failed. 



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
MattTaylor
Advocate II
Advocate II

Hi @olgaoszcz,

 

I realise this is a bit late for a reply but just in case anyone searches this in the future and spots this, I believe you can use the outputs expression to pull results of an action - you can then parse that and pull out codes or messages. 

For example: 

 
 

screenshot.png

 

Kind regards,


Matt

 

Hey Michel, the above solution will only check for a specific action. any idea how to get the error message for any action on the flow. Because most of my flow contains more than twenty actions. so, this is not a workable solution I think

Helpful resources

Announcements

Tuesday Tips: Getting Started in the Community

TUESDAY TIPS is back!   This weekly series of posts is our way of sharing helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! The original run of Tuesday Tips was a highlight of last year, and these all-new Tips will hopefully prove to be just as informative as helpful. We will cover some basics about the Community, a few "insider tips" to make your experience even better, and sharing best practices gleaned from our most active community members and Super Users. Make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   THIS WEEK: I'm Brand New! What Do I Do? The number of new community members we have each week is pretty amazing, and we are so glad to welcome all of you to the Community! You may be wondering. "What do I do? Where do I get started? Will anyone be willing to help me? What I have a question? Help!"   Let's start with this: Welcome to the low-code revolution, and more importantly, welcome to the Power Platform Community! This is a great place to start. Whether you're busy with Power Apps, getting familiar with Power Automate, engaging Copilot Studio, or building in Power Pages, there are a few key places you should check out as you begin your journey: FORUMS: The forums are THE place to ask questions, look at questions asked by other Community members—and see answers and solutions from our Super Users and other helpful people in the Community. Power Apps ForumsPower Automate ForumsCopilot Studio ForumsPower Pages Forums   NEWS & ANNOUNCEMENTS: Our News & Announcements section highlights the newest and greatest updates in the Community, news from the product team, and so much more. It’s updated a few times each week and will also help you find ways to connect with what’s going on in the ever-growing world of Power Platform. Power Apps News & AnnouncementsPower Automate News & AnnouncementsCopilot Studio News & AnnouncementsPower Pages News & Announcements   GALLERIES: The Galleries section of the Community features tons of tips and tricks, features and benefits, and more—through videos created by our Super Users, product teams, and other helpful members of the Community. Power Apps GalleriesPower Automate Galleries Copilot Studio GalleriesPower Pages Galleries BLOGS: The community blogs section is full of handy step-by-step tips from members of the Community—and some of them include detailed answers to some of the questions most frequently asked questions, as well as how they solved a problem they faced. Power Apps Community BlogPower Automate Community BlogCopilot Studio Community BlogPower Pages Community Blog POWER UP PROGRAM: If you’d like to really take a huge step forward in your journey, we recommend checking out the Power Up Program, a Microsoft-sponsored initiative that trains new Power Platform users and has been a huge success since it launched a little over a year ago. There’s a waiting list, so definitely apply soon if you’re interested! Find out more here: Microsoft Power Up Program for career switchers.   There's so much more you'll discover in your Power Platform experience, and this Community is here for YOU! We are glad you've discovered us and can't wait to see where you grow! If you're new to the Community and just getting started, make sure to give this post a kudo and introduce yourself so we can welcome you!

Super User of the Month | Drew Poggemann

As part of a new monthly feature in the Community, we are excited to share that Drew Poggemann is our featured Super User for the month of February 2024. If you've been in the Community for a while, we're sure Drew's name is familiar to you, as he is one of our most active contributors--he's been a Super User for five consecutive seasons!   Since authoring his first reply 5 years ago to his 514th solution authored, Drew has helped countless Community members with his insights and expertise. In addition to being a Super User, Drew is also a User Group leader and a Microsoft MVP. His contributions to our Super User sessions and to the new SUIT program are always welcome--as well as his sense of humor and fun-loving way of sharing what he knows with others.   When Drew is not solving problems and authoring solutions, he's busy overseeing the Solution Architecture team at HBS, specializing in application architecture and business solution strategy--something he's been doing for over 30 years. We are grateful for Drew and the amazing way he has used his talent and skills to help so many others in the Community. If you are part of the SUIT program, you got to hear some great tips from Drew at the first SUIT session--and we know he still has much more to share!You can find him in the Community and on LinkedIn. Thank you for all you do, Drew!

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. Our team will be reviewing posts using the new "Copilot Studio" label to ensure we highlight and amplify the most relevant and recent content, so you're assured of high-quality content every time you visit. If you share a post that gets featured in the curated gallery, you'll get a PM in the Community to let you know!The curated gallery is ready for you to experience now, so visit the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community. We can't wait to see what you "cook" up!    

Celebrating a New Season of Super Users with Charles Lamanna, CVP Microsoft Business Applications

February 8 was the kickoff to the 2024 Season One Super User program for Power Platform Communities, and we are thrilled to welcome back so many returning Super Users--as well as so many brand new Super Users who started their journey last fall. Our Community Super Users are the true heroes, answering questions, providing solutions, filtering spam, and so much more. The impact they make on the Communities each day is significant, and we wanted to do something special to welcome them at our first kickoff meeting of the year.   Charles Lamanna, Microsoft CVP of Business Applications, has stressed frequently how valuable our Community is to the growth and potential of Power Platform, and we are honored to share this message from him to our 2024 Season One Super Users--as well as anyone who might be interested in joining this elite group of Community members.     If you want to know more about Super Users, check out these posts for more information today:    Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

Super Users 2024 Season One is Here!

   We are excited to announce the first season of our 2024 Super Users is here! Our kickoff to the new year welcomes many returning Super Users and several new faces, and it's always exciting to see the impact these incredible individuals will have on the Community in 2024! We are so grateful for the daily difference they make in the Community already and know they will keep staying engaged and excited for all that will happen this year.   How to Spot a Super User in the Community:Have you ever written a post or asked for help in the Community and had it answered by a user with the Super User icon next to their name? It means you have found the actual, real-life superheroes of the Power Platform Community! Super Users are our heroes because of the way they consistently make a difference in the Community. Our amazing Super Users help keep the Community a safe place by flagging spam and letting the Community Managers know about issues. They also make the Community a great place to find answers, because they are often the first to offer solutions and get clarity on questions. Finally, Super Users share valuable insights on ways to keep the Community growing, engaging, and looking ahead!We are honored to reveal the new badges for this season of Super Users! Congratulations to all the new and returning Super Users!     To better answer the question "What is a Super User?" please check out this article: Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

Microsoft Power Platform | 2024 Release Wave 1 Plan

Check out the latest Microsoft Power Platform release plans for 2024!   We have a whole host of exciting new features to help you be more productive, enhance delegation, run automated testing, build responsive pages, and so much more.    Click the links below to see not only our forthcoming releases, but to also try out some of the new features that have recently been released to market across:     Power Apps  Power Automate  Copilot Studio   We can’t wait to share with you all the upcoming releases that will help take your Power Platform experience to the next level!    Check out the entire Release Wave: Power Platform Complete Release Planner 

Users online (3,495)