cancel
Showing results for 
Search instead for 
Did you mean: 

Error Handling in Microsoft Flow

As an ISV (Independent Software Vendor) and consultancy services provider specialising in Office 365 and the PowerPlatform (Flow, PowerApps and PowerBI), we spend a huge amount of time with our customers defining strategy, reviewing best practices, building solutions, fixing issues and of course reviewing previously configured solutions.

We consistently discuss how to best handle errors within Flow, and it always strikes me how few people are aware of, or make use of the 'Configure run after' feature in Flow for managing execution errors or for general workflow management.

What is the Microsoft Flow 'Configure run after' feature?

The 'Configure run after' feature in Flow allows you to control what to do given the result of a previous action, the options are depicted below:

1.png

These simple options provide some powerful error handling capabilities which can significantly increase quality and ease the operational management of production flows. For example, you can capture errors and automate support ticket logging, notify important users, execute failed operation logic, etc.

The following example provides a good and simple example of how to use the 'Configure run after' feature and a  'parallel branch' to handle an error:

2.png

If the 'Convert to PDF' executes successfully then progress and execute the 'Add Text Watermark' action, if it fails or times out we can execute the 'Send an Email' action and the 'Send me a mobile notification' action to communicate the failure.

How do I create a 'Parallel branch' in Microsoft Flow?

Interestingly and typically, when we talk to customers to the introduce the capabilities of the ‘Configure run after' feature we're consistently asked how to create a 'parallel branch'. I suspect it’s because the 'parallel branch' feature is often confused with the 'Condition' action of the 'Control' connector but they are two different capabilities.

To create a 'parallel branch' simply click 'Add a parallel branch' option located under the 'Add an action' option.

3.png

We really encourage you to make use of the ‘Configure run after' feature in conjunction with 'parallel branches'. You'll see a significant increase in the reliability and quality of your Microsoft Flows. Once you’ve started you will not be able to stop!

Comments

[0712/210044.764:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/210044.811:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/210044.811:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/210044.811:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/210044.827:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/210044.827:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/210044.827:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/210044.827:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/210044.827:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.743:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.743:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.743:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.743:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.743:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.743:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.743:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.743:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.743:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.759:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.759:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.759:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.759:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.759:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.759:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.759:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.759:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211044.759:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211545.054:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211545.054:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211545.054:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211545.054:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211545.054:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211545.054:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211545.054:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211545.054:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0712/211545.054:ERROR:crash_report_database_win.cc(469)] failed to stat report

 

shorthand debug report wondering what is necessary for stating true reportDOS

br

Meet Our Blog Authors
  • Working daily with Microsoft Cloud to deliver the needs of my company, my customers and various Microsoft communities and forums. | Office 365 | Flow | PowerShell | PowerApps | SharePoint |
  • Co-founder of https://plumsail.com, Office 365 and SharePoint expert. Passionate about design and development of easy to use, convenient and flexible products.
  • Microsoft Business Apps MVP. Owner of ThriveFast, an Office 365 consulting company.
  • 7x Microsoft Business Solutions MVP (CRM)
  • I'm keen in MS technologies, SharePoint, Office 365 and development for them
  • Daniel is a Business Productivity Consultant & Microsoft Business Solutions MVP who is very enthusiastic about all things Office 365, Microsoft Flow, PowerApps, Azure & SharePoint (Online). Since the preview, Daniel has been working with Microsoft Flow and later on with Microsoft PowerApps. That led to him being awarded an MVP Award for Business Solutions. He loves to blog, present and evangelize about improving productivity in the modern workspace with these amazing tools!
  • Michelle is an Office 365 solution architect in Twin Cities, MN. She has been delivering business collaboration solutions for years with her focus on SharePoint and Office 365. Michelle is a recent board member of the Minnesota Office 365 User Group and has been a member of the SharePoint community since 2009. She is a frequent speaker at MNSPUG and SharePoint Saturday and co-chaired the Legal SharePoint User Group for 4 years. Her most frequent projects have involved rolling out a large deployment of Office 365, SharePoint Online intranet, build of a "CHAMPS" Office 365 user adoption program and most recently, SharePoint On-Premise to Online Migration. Michelle is very excited about cloud technology as it is shifting her IT Pro focus to collaboration strategy and technical adoption.
  • I'm a Microsoft Office Servers and Services MVP with a special interest in SharePoint, Office 365, Microsoft Flow, Microsoft Teams and PowerApps. I work at Triad Group Plc ( https://triad.co.uk)
  • Passionate #Programmer #SharePoint #SPFx #Office365 #MSFlow | C-sharpCorner MVP | SharePoint StackOverflow, Github, PnP contributor