Uncovering the Overlooked Limitations of Power Automate: Why Logic Apps Might Be Your Best Bet

Overlooked limitations of Power Automate

Designing and implementing a software solution with Power Automate often feels straightforward, thanks to its easy drag-and-drop interface that caters to both end-users and IT professionals. You don’t need a computer science degree to start working with Power Automate. However, what are the limitations of Microsoft Power Automate? These limitations often become visible only when a solution is deployed in production.

The solution design phase is crucial for identifying the right technology to match non-functional requirements. A key part of this process is understanding the often-overlooked limitations of Power Automate. In this blog post, I will highlight some common mistakes that are frequently encountered with Power Automate flows. This is not an exhaustive list, but it will provide insight into the challenges you might face.

Based on my experience with low-code integrations using Power Automate and Logic Apps, I’ll offer alternative solutions using Logic Apps. Often considered the “big brother” of Power Automate, Logic Apps address several limitations that Power Automate users might overlook.

Detailed Limitations of Power Automate

Microsoft provides an official list of Power Automate limitations. It’s essential to review this list to understand the constraints you might encounter. However, this list is not exhaustive. There are additional limitations, especially with specific connector types, including third-party connectors.

Due to frequent software updates, always double-check the official Power Automate documentation for the latest information and updates. Keeping up-to-date will help you avoid unexpected issues and ensure your solutions run smoothly.

Limited run retention history

Run retention refers to the number of days you can look back in history to view an executed run. This feature is usefull for troubleshooting and compliance purposes, as historical data needs to be retained for specific periods. Power Automate has a fixed 30-day run history retention, offering no flexibility to extend this period.

Configurable Retention: Unlike Power Automate, Logic Apps allows you to configure the retention period according to your needs (up to 90 days), providing greater flexibility for troubleshooting and compliance.

Logic app standard: in the host.json file: the parameter “Runtime.FlowRetentionThreshold” configures the entire retention policy for all workflows under this logic app. The same setting is also available per workflow:

"Workflows.<workflowName>.RuntimeConfiguration.RetentionInDays"

See this blog post from Microsoft for detailed instructions.

Logic app consumption: consult this documentation for instructions how to change the history retention.

Enhanced Run History Search Capabilities

Power Automate currently lacks the functionality to search its run history using specific criteria such as time, duration, date, or status. This can make it challenging to quickly locate and analyse specific flow runs, especially when dealing with complex workflows or troubleshooting issues.

Why This Matters?

• Efficiency: Searching for specific flow runs by date, time, or status in Logic Apps saves time and enhances productivity to troubleshoot and quickly identity & analyse problems.
• Compliance: Easier access to historical data helps meet regulatory and compliance requirements.

To support the Power Automate community, I have suggested to Microsoft to include this search functionality in Power Automate. You can find and support this suggestion here. If you find this idea beneficial, please upvote it to help bring this feature to life.

Logic Apps addresses this limitation effectively by providing robust search functionality within run histories. With Logic Apps, one can easily filter and locate specific runs based on various parameters, making it a more efficient tool for monitoring and troubleshooting.

Power Platform & Power Automate Request Limits

When working with the Power Platform, it’s important to be aware of the request limits imposed by Power Automate. These limits are crucial to ensure optimal performance and compliance with licensing terms.

Understanding Power Automate Request Limits

Power Automate has specific limitations on the number of requests that can be made within 5 minutes and within a 24-hour period. These limits vary depending on the license type and apply to all actions and connector types, both successful and failed executions.

For more detailed information on these limits, you can refer to the official Power Automate Licensing documentation and Request Limits in Power Automate.

One has to keep in mind the type of licence type that’s connected with the power automate flow. Each license has a different maximum amount of requests that can be made within a time period and can’t be pooled at any other level like environment or tenant levels. Ensure to analyze these needs in advance.

How does Logic app approach this? There is no hard maximum applicable here through a form of license.

Connector Limits

Connectors are also bound to a limit, if the request limits are exceeded, you may encounter errors, such as the “429: rate limit exceeded, try again in 9 seconds” message. This can be particularly challenging for workflows that require high-frequency interactions or handle large volumes of data.

How does this work connector-specific Throttling Limits?

1. Power Automate and Logic Apps Consumption: Both require consulting the specific connector documentation to understand throttling limits. For instance, SQL managed connector limits are detailed in the SQL Server Connectors documentation.

2. Logic Apps Standard with Managed Connections: The same logic as logic app consumption applies.
3. Logic Apps Standard with Built-in Connectors: Unlike Power Automate, Logic Apps Standard offers no throttling limits due to its integration with the application plan scale-out, providing a more robust solution for high-demand scenarios.

Peak Loads and Scaling: Addressing the Need for Flexibility

Does your company need to manage peak loads or sudden bursts in demand where applications must scale up or down based on volume? While Power Automate is an excellent tool for many workflows, it falls short in scenarios requiring dynamic scaling. Power Automate does not offer configurations for scaling up or down, leading to slower performance or failed runs during high-demand periods.

Power Automate Limitations:

• No end-user scaling configurations, relies on default limitations imposed by Microsoft.
• May experience slower performance or failed runs during peak loads. (cold startup)
• Bulk data processing and high-volume requests can be challenging to manage.

Logic Apps, on the other hand, offer robust solutions for handling higher peaks:

Logic App Consumption:

• High Throughput Mode: This setting increases the throughput mode from the default 100,000 executions per logic app to 300,000 executions per 5 mins. For comparison, Power Automate has a default limit of 100,000 actions across all workflows per 5mins, while Logic Apps Consumption applies this limit to a single workflow.

Logic App Standard:

• Horizontal and Vertical Scaling: Logic Apps Standard supports both horizontal (adding more instances) and vertical (increasing resources like CPU and memory) scaling. This allows the architecture to scale automatically based on load, optimizing both cost and performance.

• Elastic Scaling: Unlike Power Automate, Logic Apps Standard can dynamically scale resources, offering elasticity to adapt to varying workloads without manual intervention.

A Need for Persistent Performance

Do you have strict performance requirements? Do you need consistent performance or work with an SLA? Power Automate Flow does not provide control over allocated resources, as it is based on a serverless model shared with others. Consequently, the performance you get will vary.

Only with Logic Apps Standard (not logic app consumption), we can configure resource management and allocation. Dedicated resources are connected to the Logic App instance, ensuring they are not competing for resources with other processes. Logic Apps Standard provides scaling options where you control the resources such as instances, memory, and CPU. By allocating these dedicated resources to your workflows, you become the sole owner of these resources, ensuring more predictable performance.

• Resource Management and Allocation: Logic Apps Standard allows for dedicated resource allocation, meaning resources like CPU and memory are exclusively assigned to your workflows, preventing competition with other processes.
• Predictable Performance: By controlling resource allocation, Logic Apps Standard provides a predictable and consistent performance, which is critical for meeting SLAs and performance requirements.
• Scalability: Logic Apps Standard supports both horizontal and vertical scaling. You can add more instances or increase resources (CPU and memory) as needed, providing flexibility and ensuring that performance remains consistent even with varying workloads.

Zero downtime deployments or fast release cycles?

In agile development environments, we aim for quick-release cycles to production. Minimizing downtime during deployment is crucial. How much downtime can your company afford during deployment? How quickly can you roll back applications if a release fails (RTO)?

When deploying a complete power platform solution with Dataverse, Power Automate and others through a solution, downtime can range from minutes to hours. For mission-critical solutions, this is not ideal.

Only Logic Apps Standard offers deployment slots to address zero downtime deployments.

These isolated, non-production environments host different versions of your app and provide several benefits:

• Seamless Swaps: Swap a deployment slot with your production slot without interruption. This allows you to update your logic app and workflows without affecting availability or performance.
• Safe, Read-Only Testing: Validate updates in a read-only staging environment, so you know exactly what will go live.
• Easy Rollbacks: Roll back to a previous version if something goes wrong with your deployment.

Managing Multiple Developers in a Power Platform Team

Are you working with multiple developers on a Power Platform solution? Keeping track of changes, rolling back, or comparing environments can be challenging. Currently, Power Automate doesn’t directly integrate with a localhost execution and source control. However, it’s not impossible. By customizing your CI/CD process, you can achieve some integration.

Power Platform exports solutions as zip files, which are then loaded into the new environment. There isn’t built-in source control integration, but we have Power Platform also offers options for creating CI/CD release pipelines for Application Lifecycle Management (ALM).

Both Logic Apps Standard and Consumption integrate with source control. Logic Apps Standard simplifies the release process by housing multiple workflows within a single resource, similar to Power Platform solutions. In contrast, Logic App Consumption requires more effort per workflow due to its specific resource nature.

Setting up resources, environments, or new connections in Logic Apps? Infrastructure as Code (IaC) tools like Bicep or Terraform make it easy. However, setting up end-to-end pipelines is still a technical task that doesn’t come with wizard-style simplicity like Power Automate pipelines. This setup offers more flexibility and options.

Conclusion: Finding the Right Tool for the Job

This blog post turned out longer than expected and is not intended to suggest that everyone switch to Logic Apps. Instead, it is designed for those facing specific needs and seeks to provide alternative solutions within the Microsoft landscape.

Before starting development, it is essential to gather requirements and outline the architecture. Understanding the power platform limitations before development is crucial because real software developers don’t test in production.

By considering the common mistakes and overlooked limitations of Power Automate, you can make informed decisions and choose the right tool for your project. Remember, both Power Automate and Logic Apps have their strengths and weaknesses. The key is to match the tool to your specific requirements to ensure a successful and efficient solution.