In my series of error handling posts I’ve looked at

In this post I’m going to have a look at error handling in small flows. Huh, is that any different?

Not, really but when you have small flows with some action that could fail then you could consider a flow structure like this:

Parallel Error Handling

When an action fails you will see the flow going into the failed section of your flow.

Parallel Failed

And when an action is successful the flow will continue in the Success branch.


Parallel Succeeded

All of this can be done with parallel actions.  You will find however that adding 4 branches after every action is less practical than the try / catch approach but for smaller flows this could be a good pattern to follow. Potentially you could even simplify the pattern by merging the Failed, Skipped and Timeout into one branch. That way there is a did run  and a did not run branch. And having two branches after each potentially failing action you might find that this pattern becomes more manageable.




By Pieter Veenstra

Business Applications and Office Apps & Services Microsoft MVP working as a Microsoft Productivity Principal Consultant at HybrIT Services. You can contact me using

One thought on “Microsoft Flow – Error Handling for small flows”

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: