These are my top 10 #Tips&Tricks to improve performance when working with Microsoft Power Automate
Tags: powerfuldevs, microsoft365, powerplatform, powerautomate
Published: 2023-03-04 05:00:14

Hello automation aficionados! If you're like me, you're always on the lookout for new ways to optimize your workflows and make your life easier. That's where Microsoft Power Automate comes in! But even if you're already familiar with this handy tool, there are always ways to improve its performance and make your workflows even more efficient. That's why I'm excited to share my top 10 tips and tricks for Power Automate. From trigger conditions to "Terminate" actions, these hacks will help you to improve your workflows and get the most out of this powerful tool. So let's dive in!



## Use trigger conditions to filter out unnecessary events##

Trigger conditions are like filters that you can use to make sure a Power Automate flow only runs when certain things happen. For example, you might want your flow to run only if a specific field in a SharePoint list is set to a certain value. By adding a trigger condition to your flow, you can make sure it will only run when that specific condition is met. 

![Click on the trigger to open its properties and select "Settings" to open the trigger editor and add your condition.](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/n2ok0eq79qs30piyukrq.png)
> _Click on the trigger to open its properties and select "Settings" to open the trigger editor and add your condition._

Using trigger conditions can also help you create more targeted flow that are customized to your specific needs. For instance, if you only want a flow to run for certain items in a list that holds Approval Status equal to Pending, you can add a trigger condition to filter out all other items and focus only on those that meet your criteria. This can help you save time, prevent infinite loops and make your flows more efficient overall.

---


## Use "Filter array" action to build more complex trigger conditions##


![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/mvor99vz1yx7lf6y8txp.png)
>_Add a "Filter array" action after the trigger  > From: Output from the trigger > Add the dynamic content to the condition > Click: Edit in advanced mode.

and Voilà_


---

## Use the "Scope" action to group related actions together##

The "Scope" action allows you to group related actions together, making it easier to manage complex flows. By grouping related actions together, you can improve the performance of your flows and reduce the risk of errors.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/9a4m5xaq9zja4v6ous6d.png)



---

## Use the "Run after" feature to manage errors and exceptions##

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/r3jf3eq3rscm3o6wugga.png)
> _Click on the action to open its properties and select "Configure run after"_

The "Run after" feature allows you to manage errors and exceptions in your flow. By using the "Run after" feature, you can specify what actions should be taken if an error occurs or if an exception is thrown. This can help to ensure that your flow continues to run smoothly, even when unexpected errors occur.




---

## Use timeout durations with approval flows##

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/gu6iumx0x6622uvreiy9.png)
Approval flows can be configured to require approval from one or more users before continuing with the workflow. By setting a timeout duration on the approval action, you can specify how long the workflow should wait for the approval before taking action. This can be useful for ensuring that workflows don't get held up waiting for approvals that may never 

> _The duration format "P1D" represents a time duration of one day in ISO 8601 standard. You can also use other time duration formats, such as "PT2H" for a duration of two hours, etc.
Approval flows can be configured to require approval from one or more users before continuing with the workflow. By setting a timeout duration on the approval action, you can specify how long the workflow should wait for the approval before taking action. This can be useful for ensuring that workflows don't get held up waiting for approvals that may never come._


---

## Use concurrency control in the "Apply to each"##

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/i7zlcjy4qeqn13exie61.png)
>_By setting the degree of parallelism to 50, you are telling Power Automate to process up to 50 iterations of the loop simultaneously, which can significantly reduce the overall execution time of the flow._

I use concurrency control to decrease the execution time of the "Apply to each" action. This is especially useful when working with large amounts of data, where processing each item sequentially can take a long time.



---

## Copy and Paste actions##

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/i8z5q33n6iy1wg00z8x5.png)
By selecting "Copy to my clipboard" it extract the text generated by the action inclusive dynamic content or expressions in the input box. Use CRTL+V to paste the text into the "My clipboard".



---

## Use the "Get changes" action in SharePoint to monitor changes to lists and libraries.##

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ngjtq0fl6soqiybhohp8.png)
By using the "Get Changes" action in Power Automate, we can identify if any column has been modified, retrieve the changes made to items in a SharePoint list or library. This action allows you to track changes based on a certain time period or specific criteria, such as changes made by a specific user or changes to a specific column.



---

## Last but not least: Naming convention##


![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/l8v5kjgezmri4occ0hvl.png)
Establish a consistent naming convention for all your flows and stick to it. This makes it easier to search for and find your flows, and ensures that they are organized in a logical way and have descriptive names that accurately reflect the purpose of your flow. Avoid generic names like "Flow1" or "Untitled Flow".




---

###Conclusion 📝###
By adopting clever naming conventions, using trigger conditions to your advantage, and making the most of concurrency control, you'll be able to maximize your flow's efficiency and get things done faster. And don't forget the importance of testing and troubleshooting. So take advantage of these Tips&Tricks and achieve great success with Microsoft Power Automate!