Looking to systemically track cloud and desktop flow errors into a SharePoint or database for team to follow-up and address flow failures. I know PA provides monitoring online through PA monitoring.
https://make.powerautomate.com/ > Monitor
Cloud flow activity > Failures
Desktop flow activity > Errors
However, this doesn't allow team to share RCA, Resolution notes (error closure), and flow history.
From enterprise solution how can this be done systemically? Anyone have solution they have successfully implemented?
Again, Solution needed for both Cloud and desktop flows.
Solved! Go to Solution.
HI @automateall ,
I'll share a couple things I am doing that has helped me.
Cloud flows: configure your run-after action settings and turn on failures and timeouts, also capture the error messages. Right now I am emailing myself so I can see them immediately and has been working well (but could go into a List with status and on-going notes).
Desktop flows: I have a subflow on all my desktop flows that is launched when my onBlock catches an error. In my sub flow, I am closing applications, windows, browsers, logging out of things open, etc, but most importantly, I am taking a snapshot of the desktop to help me see what actually occurred and the current variable values if relevant (works great most of the time). If you are running unattended flows, you can also capture the last error message and send it back to cloud flow and include in your email notification. I am saving all my error snapshots to a folder for any other developers to review OneDrive/SharePoint (also working well).
Obviously, it doesn't have to be an email, it could go into a List too but for me, what has worked is getting the notification immediately (plus use monitor and history, and flow access) and troubleshooting in real-time. To track history, notes, resolutions etc, implement managed solutions and document your flows well in your test environment. Goes without saying, if you bullet proof your production environment solutions, you should have a small list of errors to triage if you are using a good ALM strategy.
Please mark as a solution ✅ and/or give me a thumbs up 👍🏽 for replying and volunteering my time! 🎗️ Always glad to help! Tom ⭐⭐⭐⭐⭐
HI @automateall ,
I'll share a couple things I am doing that has helped me.
Cloud flows: configure your run-after action settings and turn on failures and timeouts, also capture the error messages. Right now I am emailing myself so I can see them immediately and has been working well (but could go into a List with status and on-going notes).
Desktop flows: I have a subflow on all my desktop flows that is launched when my onBlock catches an error. In my sub flow, I am closing applications, windows, browsers, logging out of things open, etc, but most importantly, I am taking a snapshot of the desktop to help me see what actually occurred and the current variable values if relevant (works great most of the time). If you are running unattended flows, you can also capture the last error message and send it back to cloud flow and include in your email notification. I am saving all my error snapshots to a folder for any other developers to review OneDrive/SharePoint (also working well).
Obviously, it doesn't have to be an email, it could go into a List too but for me, what has worked is getting the notification immediately (plus use monitor and history, and flow access) and troubleshooting in real-time. To track history, notes, resolutions etc, implement managed solutions and document your flows well in your test environment. Goes without saying, if you bullet proof your production environment solutions, you should have a small list of errors to triage if you are using a good ALM strategy.
Please mark as a solution ✅ and/or give me a thumbs up 👍🏽 for replying and volunteering my time! 🎗️ Always glad to help! Tom ⭐⭐⭐⭐⭐
For desktop flows, we generally use JSON logs on a plain text file stored locally on the machine, but then have ELK stack set up to retrieve, parse and store those logs. So, we can always monitor the logs of each flow during runtime, if needed. This applies not only to error logs, but also informational messages that we also log, which are intended to help debug issues when they appear.
The general idea for logging in Desktop flows is using the On block error action to add some rules when an error occurs, then using the Get last error action to get the error details. This action returns a lot of details that are usually enough to handle any system exception. But if you also want to log business exceptions, you will also need to set some log messages manually. And then you need a sub-flow that logs the message somewhere. As mentioned, we use JSON into a plain text file. But you can also easily push those logs to a database or a SharePoint list. Both are perfectly viable options in PAD.
As to cloud flows, I suggest reading this article: https://dev.to/wyattdave/exception-handling-in-power-automate-4c4h
It has some great suggestions on how to handle errors. It does have some mistakes in some of those expressions that doesn't always work (especially in more complex structures), but once you get the general idea, you can easily implement that yourself, too. And, instead of sending those messages to yourself via email, you can also push them to a database or a SharePoint list. These are also perfectly viable options in PA cloud, too.
We usually send those errors via email to our support mailbox that is shared between the team, or a shared mailbox at the client side, where the relevant people can all see it.
-------------------------------------------------------------------------
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.
I also provide paid consultancy and development services using Power Automate. If you're interested, DM me and we can discuss it.
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
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** 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. Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages