Tag: PowerAutomate Tips

Power Automate performance improvement considerations

Hi Folks,

Thanks for visiting my blog…in this blog post, have you ever faced the situation where your flow keeps running with no output. Today I will list down the possible scenarios where you were struck with slow performance of the Flow.

Consider the below actions to make your flow execute smoothly.

Remediation steps/Actions to take to make your flow run efficiently:

  1. Understand the throttling limits for your connectors and data sources
  2. Check for Request limits based on user licenses
  3. Cross verify the throughput limits
  4. See the minimum number of actions that the Power Automate service will allow for each plan on the Request limits and allocation page.
  5. Do verify if you were using any on premise connectors
  6. You are hitting the throttling limit in Power Automate
  7. Redesigning your flow to use fewer actions and less data.
  8. Reduce the number of loop iterations for the iteration in ‘Do Until’ and ‘For each item’
  9. Filter your data to retrieve only what is necessary Filtering with Odata
  10. Consider reducing the frequency of scheduled cloud flow
  11. Reduce the file size being accessed if possible if your flow uses them
  12. Consider using Variables for frequently accessed information in your flow
  13. Use Compose and Variable actions to view the data at any time.
  14. Purchasing a Per User or Per Flow license from the pricing page
  15. Per Flow plan may provide best performance quotas available
  16. Enable concurrency control for your ‘Apply to each’ action
  17. Consider creating custom retry policy
  18. Use Select Actions
  19. Check your System jobs in Data verse if asynchronous service performance is normal
  20. Reduce the flow complexity
  21. Consider using Process Advisor for Power Automate.
  22. Verify if you were hitting 2 minute timelimit in dataverse if you were calling Bound or Unbound action in Flow.

Hope this helps someone who’s looking to optimize their flow.

Cheers,

PMDY

Top picks for Power Automate

Orphan Flows in Power Automate??

If you are a Dynamics CE Consultant, you should have heard of orphan records. Do you know Orphan flows do exist in Power Automate in a similar way….

A flow is considered to be an Orphaned flow when it don’t have a valid owner anymore. This can possibly happen when the creator or owner of the flow has left the organization and there is no co-owner or the owner for the flow. If the flow uses connections that require authentication, then it may start failing because the user identity is not valid anymore.

Admins can maintain continuity on the business process automated by the flow by adding one or more co-owners to it. Co-owners basically have full control over the flow just like the original owner, and can fix authentication for connections if any and enable the flow if it has been disabled.

Please note that only privileged users can view flows that do not have any valid owners. On the environment page from Flow Admin Center (https://admin.flow.microsoft.com/environments), go to “Resources” tab and then open the “Flow” list. Orphaned flows display “None” as their owner.  Click “Load more” to load the next set of flows so as to ensure you have looked through all flows that might be orphaned.

How will you solve this problem?

  1. Manually you can add the flow a owner which will resolve the issue when the number of flows are in reasonably small in number. But if the number of Orphaned flows are in large number, you should look for next approach presented.
  2. Code way…using Power Automate cmdlets: Make sure you follow the instructions for setting this up.

Reference: How to manage orphan flows when the owner leaves the organization

Cheers,

PMDY