Parallel Branches in Power Automate: A Comprehensive Guide with Examples

Power Automate (formerly known as Microsoft Flow) is a powerful tool for automating repetitive tasks and streamlining business processes. One of the most advanced features in Power Automate is the parallel branches functionality, which allows you to execute multiple actions or processes concurrently, rather than sequentially. This leads to faster execution times and more efficient workflows.

In this article, we'll explore how parallel branches work in Power Automate, their benefits, and how they can be applied through real-world examples. We'll also cover scenarios where timeouts or errors may occur and how to handle them gracefully within parallel branches.

What Are Parallel Branches in Power Automate?

Typically, workflows in Power Automate run step by step, where each action waits for the previous one to complete before starting. However, some tasks can be performed independently and concurrently. Parallel branches allow you to split your workflow so multiple actions can occur at the same time. This is especially useful when you have tasks that are independent of each other or when you want to speed up execution by running things simultaneously.

For instance, imagine a scenario where you need to notify several departments about a new policy. Instead of sending these notifications one by one, you can use parallel branches to notify all departments at the same time.

Benefits of Using Parallel Branches

There are several advantages to using parallel branches in Power Automate:

1. Improved Efficiency: Since actions in different branches can run simultaneously, workflows are executed faster.

2. Reduced Delays: By avoiding sequential execution, you can run independent tasks at the same time, minimizing bottlenecks.

3. Optimized Resource Utilization: Parallel branches allow you to better utilize system resources by distributing the workload.

4. Clear Workflow Design: Workflows with parallel branches are often easier to read and maintain, as they visually represent simultaneous actions.

Creating Parallel Branches in Power Automate

Power Automate makes it simple to create parallel branches in a flow. Here's how you do it:

1. Start Your Flow: Begin by designing your flow and adding a trigger.

2. Add Actions: Add actions to your flow as you would normally.

3. Add Parallel Branches: Hover over an existing action, click the "+" icon, and select "Add a parallel branch." You can then configure additional actions that will run concurrently.

4. Configure Each Branch: Set up the actions in each branch independently, specifying the conditions, data, and logic for each task.

Example 1: Send Notifications and Update a Database in Parallel

Scenario:

Imagine a scenario where a form is submitted, and you need to notify a stakeholder and update a database with the form data simultaneously.

Steps:

1. Trigger: Start the flow with the trigger “When a new item is created” in a SharePoint list.

2. First Parallel Branch - Send Notification: Add an action to send an email notification to the stakeholder.

3. Second Parallel Branch - Update Database: In the second branch, add an action to insert the form data into a SQL database.

By using parallel branches, the flow will send the email and update the database at the same time, significantly reducing wait times.

+ Trigger: When a new item is created

+ Parallel Branch 1: Send an email notification

+ Parallel Branch 2: Update SQL Database

Example 2: Parallel Approvals from Multiple Departments

Scenario:

You have a process that requires approval from several departments—such as finance, HR, and IT—before moving forward. Using parallel branches, you can request all approvals simultaneously, speeding up the process.

Steps:

1. Trigger: Use the trigger "When a purchase request is submitted."

2. Parallel Branches for Approvals:

In the first branch, add an approval action for the finance department.

In the second branch, add an approval action for HR.

In the third branch, add an approval action for IT.

3. Final Action: Once all approvals are obtained, notify the requester or proceed with the purchase process.

This setup ensures that approval requests are sent simultaneously, speeding up the entire process.

+ Trigger: When a purchase request is submitted

+ Parallel Branch 1: Finance Approval

+ Parallel Branch 2: HR Approval

+ Parallel Branch 3: IT Approval

Example 3: Parallel Data Collection from Multiple Sources

Scenario:

Suppose you need to collect data from several sources—such as SharePoint, SQL Server, and a third-party API—and generate a consolidated report. By using parallel branches, you can fetch the data from each source concurrently.

Steps:

1. Trigger: Start the flow with a trigger like "Manually triggered flow."

2. Parallel Data Collection:

In the first branch, fetch data from SharePoint.

In the second branch, fetch data from SQL Server.

In the third branch, call the third-party API for additional data.

3. Combine Data: After all branches complete, consolidate the data into a single report.

This approach minimizes the overall time spent collecting data from multiple sources.

+ Trigger: Manually triggered flow

+ Parallel Branch 1: Fetch data from SharePoint

+ Parallel Branch 2: Fetch data from SQL Server

+ Parallel Branch 3: Call third-party API

Example 4: Parallel Document Generation and Approval

Scenario:

You want to automate a document creation process where once a document is generated, it should be sent for approval and simultaneously logged into a document management system.

Steps:

1. Trigger: Use the trigger "When a new file is created in a document library."

2. Parallel Branches:

In the first branch, send the document for approval.

In the second branch, log the document into the document management system (DMS).

3. Final Action: Notify the document creator once both processes are completed.

By using parallel branches, the document approval and logging happen simultaneously, reducing the overall process time.

+ Trigger: When a new file is created in a document library

+ Parallel Branch 1: Send for approval

+ Parallel Branch 2: Log document in DMS

Example 5: Parallel API Calls for Real-Time Data

Scenario:

You are building a dashboard that needs to retrieve information from multiple APIs (e.g., weather, stock prices, and currency exchange rates). These tasks can be run in parallel to speed up data retrieval.

Steps:

1. Trigger: Use the trigger "When a button is clicked."

2. Parallel API Calls:

In the first branch, call the weather API.

In the second branch, call the stock price API.

In the third branch, call the currency exchange API.

3. Display Results: After all branches complete, display the data in your dashboard.

Running these API calls in parallel minimizes the total time needed to gather the data for the dashboard.

+ Trigger: When a button is clicked

+ Parallel Branch 1: Call Weather API

+ Parallel Branch 2: Call Stock Price API

+ Parallel Branch 3: Call Currency Exchange API

Example 6: Handling Timeouts and Errors in Parallel Branches

Scenario:

In some cases, you might have parallel tasks that take too long to complete or encounter an error. For example, you have a flow where one branch makes an API call, and another performs a database update. If the API call takes too long, you want to handle it with a timeout action. Similarly, if any branch encounters an error, you want to log the error and continue processing.

Steps:

1. Trigger: Use a trigger like "When an HTTP request is received."

2. Parallel Branches:

First branch: Call an external API.

Second branch: Perform a database update.

3. Timeout Handling:

Use the "Configure Run After" option in Power Automate to handle the timeout in the API branch. If the API call times out, log the timeout and proceed with the database update.

4. Error Handling:

Configure both branches to catch any errors (e.g., network failures, missing data) and log the errors before continuing the flow.

This setup ensures that even if one branch encounters a problem, the entire workflow doesn't fail, and you can take corrective actions or log the issue.

+ Trigger: When an HTTP request is received

+ Parallel Branch 1: Call external API (with timeout configuration)

+ Parallel Branch 2: Perform database update

+ Error Handling: Log any errors encountered

Summary

Parallel branches in Power Automate offer a powerful way to improve the efficiency and speed of your workflows by allowing actions to run concurrently. Whether you're sending notifications, collecting data, handling approvals, or making API calls, parallel branches can significantly enhance the performance of your automation processes. Furthermore, by incorporating error and timeout handling, you can make your flows more robust and reliable.

By using the examples provided in this article, you can start leveraging parallel branches to streamline and optimize your business processes, saving time and resources in the process.