Power Platform Community Forum Thread Details

Basically, new versions of Power Automate break and old versions work. Something on my network is blocking PAD 2.49 but works with earlier versions. How can I identify what has changed?

I have an issue that I have been trying to work through for a couple of weeks (not full time). On some systems I open a flow and get a "Flow initialization failed. Please make sure there is an active internet connection and contact your administrator." error. I open the same flow on other systems and I don't get the error. It doesn't seem to matter what flow it is, just that it is recently saved and on a recent version of power automate. Here is one test scenario:

I create a new flow on one system running version 2.49.177.24289
I save it without adding any tasks
I close the flow
I reopen and get "Flow initialization failed. Please make sure there is an active internet connection and contact your administrator."
- Same system. A couple of seconds later.
I open it on another system (version 2.42.317.24061) it opens fine
- Same login
- Same Network Policies

Test Scenario 2

I take an old flow
- It was an old abandoned ad-hoc flow.
I can open it on the systems running 2.49 and 2.42
Once I save it on the 2.49 system. I get the same error. The 2.42 system works fine

I'm pretty sure that the more recent versions of Power Automate are adding something that my security team has blocked.

How can I find out what it is?
- Is there somewhere that will actually tell me what is blocked?
How can I get the install files for a prior version of Power Automate to validate my hypothesis?

Categories:

General topics