In this post I’m looking at performance of Power Automate flows. For some flows this may not really matter too much, however when you have a need to high performance flows the findings in this post may be quite important. To make your flows perform well, it is important to understand where time is wasted.
Author: Pieter Veenstra
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like.
I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide.
For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions.
You can contact me using contact@sharepains.com
I will start this post with a warning about the New Designer Run After settings. The steps described in this post do not make it easier to understand what your flow will do. But I’m sure someone will comment on this post with a “That is exactly what I need”
Today I’m looking at the Tenant Level Analytics setting. The Power Platform Admin Center is getting more and more features that we would have used
On a Power Platform project with multiple developers Connections and Connection references can be tricky. You have some connection references added to a solution by
For many years I’ve been saying, don’t use variables in Power Automate as it hurts the flow’s performance. Recently it was pointed out to me
Load More