web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Try/Catch/Finally para...
Power Automate
Unanswered

Try/Catch/Finally parallel branch scope

(0) ShareShare
ReportReport
Posted on by 1,599 Super User 2024 Season 1

Hello,

 

I have built a complex flow with multiple parallel branches with the same actions in.

I have put these into a scope with the thought of using a Try/Catch/Finally technique for error handling.

 

You can see how this is structured below. There are about 6-7 parallel branches spread across 3 Try scopes (6-7 in each scope).

sudosaurus_0-1699034221588.png

I was following this article, however I'm unsure how I'd implement this given that I have multiple branches in one scope rather than the one shown: https://softchief.com/2022/06/30/power-automate-exception-handling-using-try-catch-finally/

It would be helpful to get some pointers as how best to achieve this?

Thanks!

Categories:
I have the same question (0)
  • Jcook Profile Picture
    7,781 Most Valuable Professional on at

    Hi @sudosaurus 

     

    In your flow everything is in 1 scope. That’s your “Try”.

     

    you can have another scope after your “Try” as the catch for errors.

  • sudosaurus Profile Picture
    1,599 Super User 2024 Season 1 on at

    @Jcook - how do I catch errors from the Create/Update file actions?

  • grantjenkins Profile Picture
    11,063 Moderator on at

    Below are two different options.

     

    Option 1: Use a scope for each parallel branch. However, you would still need to handle the errors within each parallel branch which would mean more duplication.

    grantjenkins_0-1699151291070.png

     

    Option 2: Main/Child - Set up just a single flow (no parallel branch) and call it from another flow passing in the data you need to differentiate each branch (Payroll, OOH, etc.). This is how I'd go about it as you would only need to build a single branch (not duplicate all the actions). With this you can choose to return the error back to the main flow, or handle it (Try, Catch, Finally) within the child flow (I'd likely handle it within the child flow in this instance).

     

    For Option 2, can you let me know the following:

    1. What is your main trigger?
    2. What data would you expect to pass in to the child flow (apart from Department)?
    3. Do you have access to Premium connectors such as When a HTTP request is received?
  • grantjenkins Profile Picture
    11,063 Moderator on at

    Just a quick note. If you are passing the value from Get files (properties only) - Battelbox-Payroll into the Apply to each 9, then there's no point having the Condition to check if the length is greater than 0. If the length is 0 then the Apply to each 9 wouldn't even run since there are no items to iterate over.

     

    grantjenkins_1-1699157628795.png

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 519 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 296 Moderator

#3
abm abm Profile Picture

abm abm 232 Most Valuable Professional

Last 30 days Overall leaderboard