Microsoft Power Automate Problems & Issues
Real user-reported problems, complaints, and limitations for Microsoft Power Automate. Based on analysis of 13 signals.
Overall score: 58/100
Issues by Category
Power Automate flow not triggering
Triggers stop firing because of expired connections, DLP policy violations, trigger conditions, admin mode or a failed trigger registration. Forum threads describe silent failures with nothing in run history.
Flows turn off or get suspended without warning
Microsoft documents that flows with continuous failures or constant throttling are turned off after 14 days and flows with no trigger activity after 90 days unless the owner holds a premium license. Reviewers and forum users report flows stopping and needing monitoring.
Desktop flows fail unattended
Desktop flows that work attended break unattended because of screen resolution, a locked or active user session, a stopped UI flow service or changed selectors. Microsoft has dedicated troubleshooting guides for this.
Excel 'table not found' and Add a row errors
Excel actions only work on formatted tables, not plain ranges, and forum users report flows that ran for weeks suddenly failing with 'No table was found' or intermittent errors that clear on re-run.
Power Automate licensing is confusing and hard to predict
G2 reviewers repeatedly call the licensing model complex and not transparent. Which plan covers a flow depends on the connector, the trigger type and who runs it, and the Microsoft 365 plan does not cover premium connectors.
Premium connectors need a paid license
Standard connectors come with Microsoft 365, but premium, on-premises and custom connectors need a Power Automate Premium or Process license. Microsoft documents that users running or editing such flows need their own license for manual flows, and a 90-day trial ends in failures.
Why is Power Automate so expensive for small teams?
Premium is $15 per user per month billed yearly and Process is $150 per bot per month. Reviewers say small businesses feel the cost of premium features most, and sharing one flow across many users pushes teams toward per-flow licensing.
Error messages are unclear and debugging is hard
G2 reviewers say debugging complex flows is difficult and error messages are often unclear. Microsoft itself ships Copilot troubleshooting and repair-tip emails to compensate.
Large flows get hard to edit and maintain
Microsoft documents a 500 action limit per flow and warns that flows with many actions can be slow to edit. Reviewers report weak versioning and difficult collaboration between developers.
Non-Microsoft integrations need more work
Reviewers say connecting to non-Microsoft systems takes extra configuration compared with Zapier, and some mention difficulty with Teams and Snowflake connections. Many comparison sites list connector depth as the top reason to leave.
HTTP trigger URLs changed in the architecture move
Flows with HTTP or Teams webhook triggers on the Logic Apps architecture had their trigger URLs replaced, with old URLs stopping on November 30, 2025, and new URLs can exceed 255 characters with SAS auth.
Flows are slow or throttled with 429 errors
Connector throttling, daily action limits per plan and slow downstream services make flows slow. Microsoft documents SharePoint at 600 calls per minute per connection and a 429 'Rate limit is exceeded' error.
DLP policy changes silently break flows
Admin data loss prevention changes take effect immediately and can suspend flows. Microsoft says that if many flows broke at once, a DLP change is the most likely cause, and makers often see only 'workflow is disabled by your organization'.
Regret Patterns
Common reasons users regret choosing Microsoft Power Automate.
Built on a premium connector, then hit the license wall
A flow is built with a premium connector during a trial or on a developer account. When it moves to production or the trial ends, it fails until each owner or user is licensed.
Flow quietly stopped and nobody noticed
A flow suspended for failures, throttling or inactivity, or a connection token expired, and no one monitored run history, so the process silently stopped.
Flow worked for the maker but not for colleagues
A shared instant flow ran fine for the owner but failed for users without the right license or connection permissions.
Moved to Process licensing after volume grew
A flow hit daily action limits and throttling, and the fix was a $150 per bot per month Process license or an export to Logic Apps.
Hard to debug a long flow with vague errors
A growing flow with many actions produced unclear errors and was hard to version or hand over.
When Microsoft Power Automate Breaks Down
Specific scenarios where Microsoft Power Automate fails or underperforms.
The owner leaves the company
A cloud flow uses the owner's plan and connections. Microsoft documents the flow reverting to the Low performance profile when the original owner leaves, and personal connections can break.
A connection password or MFA policy changes
OAuth tokens become invalid after a password change or MFA change, and refresh tokens expire after about 90 days of inactivity, so flows fail with 401 errors.
Bulk processing of thousands of rows
Loops hit throttling and daily action limits, SharePoint's 5,000 item list view threshold or Excel table limitations.
Admin changes a DLP policy
Connector classification changes take effect immediately and can suspend many flows at once.
Unattended desktop flow on a locked or changed machine
A different screen resolution, an active user session or a stopped UI flow service makes a flow that worked attended fail.
Trial of Premium ends
Flows that use premium connectors fail on the premium action until a paid license is assigned.