General Power Automate Performance Issues

(2) Share

Report

Posted on by BANDOVS

Is anyone else seeing performance issues with basic website navigation on make.powerautomate.com?

I'm seeing this on UK environments on multiple tenants.

Very slow to load pages, failures saving flows.

Cannot create a new outlook 365 connection - https://uk-001.consent.azure-apim.net/

Categories:

General topics

I have the same question (0)

All responses (6)

Answers (1)

Sort by

Vish WR 2,825 on at

Like (2)

Report
Copy link

Link copied!

@BANDOVS

I am from the Singapore region, was using power automate todat i did not experience any issues on slowness and failure on saving the flow

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
ksm12 13 on at

Like (2)

Report
Copy link

Link copied!

I am seeing these issues in the UK, powerapps slow and also powerautomate

Was this reply helpful? Yes No
Suggested answer

Haque 2,985 on at

Like (3)

Report
Copy link

Link copied!
Hi @BANDOVS,

Can we check these two points?

Check Microsoft 365 Service Health: Let's check service health dashboard (if you have admin access) to see if there are any ongoing incidents or advisories affecting Power Automate or Azure API Management endpoints in your region.

Try alternative environments or regions: If possible, test the same actions in a different environment or region to see if the issue is isolated to UK datacenters.

Was this reply helpful? Yes No
Verified answer

BANDOVS 25 on at

Like (2)

Report
Copy link

Link copied!

Raised an issue with MS support. This is what they said:

We sincerely apologize for the inconvenience experienced. I can confirm that the issue you are encountering is due to a global outage, which our Product team is aware of and is actively working to resolve. There are multiple users currently affected by this issue.

We kindly ask for your patience while our Product team continues to investigate and deploy a fix across all impacted regions.

There appear to be 3 related issues logged:

6362251 | Power Platform admin center

6362460 | Power Platform admin center

6362401 | Power Platform admin center

Edit - and another: https://admin.powerplatform.microsoft.com/support/knownissues/6356365

Thanks @jess23

Was this reply helpful? Yes No
jess23 8 on at

Like (3)

Report
Copy link

Link copied!

This has also been reported, still active as of 8/5/2026 so watch this space.

Issue ID 6356365: Power Automate flow editor memory issues

Product: Power Automate

Created on: 05/05/2026 7:19 AM AEST

Problem
Power Automate flow editor crashes with out of memory errors when opening or editing complex cloud flows. Users cannot save changes due to browser memory limitations.

Workaround

We are aware of an emerging issue with the Power Automate Flow Designer where users may encounter errors loading flows in the designer for editing. The fix for this issue is rolling out over the next few weeks.

Link: https://admin.powerplatform.microsoft.com/support/knownissues/6356365

Was this reply helpful? Yes No
originalltd 89 on at

Like (0)

Report
Copy link

Link copied!

In our Power Automate environment, we are having massive issues with flows that contain SQL Connections, or are complex flows.

Here are a list of issues we are experiencing:

- Out of Memory (Microsoft Edge). The browser window shows "This page is having a problem". It usually appears a few minutes after the flow has loaded.

- Invalid Parameters. This is showing on all SQL Server flows.

- Variables have lost their inputs, resulting in failed flows.

- SQL Server Name and Databases are defaulting to "Default" and not the server name or database name.

So as it stands, we cannot edit flows or fix them.

This is a known issue in PowerAutomate - accessible at: 6356365 | Power Platform admin center

Microsoft say the fix is deploying to environments which make take WEEKS!

Was this reply helpful? Yes No