This post is all about error handling and parallel branches.
General error handling in Power Automate
In the past I’ve written quite a few posts about the Try-Catch pattern. Which handles a lot of error handling issues. Yesterday I was asked about how to handle errors in parallel branches.
As an example I build the following flow with parallel branches in Power Automate:
Just a bunch of compose actions. Compose 2 in the right branch is failing. Then Compose 3 is skipped as its previous step failed. And then Compose 5 has all the run after settings set.
What would you expect to happen with Compose 5 will it run?
Well I put it to the test. and Compose 5 is skipped.
So how should we handle the error? We want compose 5 to run!
Time to look at some of my try catch posts again.
How about creating a try catch in both my parallel branches? For simplicity sake I’m only building it in the right one, but each branch should have a try catch in it.
The catch’s run after settings are to include failed and skipped and potentially you should also include the timed out option
And now my flow runs successfully.
Well, we need to look at the Run after settings a bit more and I’m going to go back to the version of the flow without the try and catch pattern applied.
You migth think that this flow is now going to run for all states, but it is not.
Note on the right hand side the two boxes! Compose and Compose 3. Click on Compose 3 and you will see the answer to our question!
We need to zoom on on that Compose 5 action.
For each last action in each branch you can set a separate run after settings. Thanks John Liu for pointing this out.
The preceding options are clearly listed on the left hand side. However that they are clickable wasn’t obvious.
For error handling in parallel branches it is important to understand that you can click on this actions on the left hand side of the run after settings.