Building error handling into your Microsoft Flows
Whilst building Flows I often come across situations where my Flow experiences an error and just stops. This isn’t necessarily what I want to happen so we need an effective way to handle it and makes some intelligent decisions based on what’s happened.
Sometimes we don’t care if an action fails and we just want to carry on. Sometimes we want to perform different actions based on whether an action is successful or fails and sometimes we want to roll back any previous changes in the Flow.
The easiest way to manage error handling in Flows is to use the built in “Configure run after” setting. This gives you the ability to make intelligent routing decisions based on the success of Flow Actions.
You have four options: is successful, has failed, is skipped, has timed out.
They are pretty self explanatory.
The easiest way to have different routes is to run parallel tasks that are configured to run after a particular Action or Actions. These will be triggered on success or failure. Oftentimes, I just have those parallel branches set up to set a variable and then drop out of the parallel section and run a conditional branch.
It’s pretty simple when you know about the “configure run after” ability and get your head around effective routing.
Put enough error handling in place and you’ll end up with a “lefty Flow” as I like to call it! You’ll see what I mean!