Error message - Flow initialization failed.

(0) Share

Report

Posted on by stevec63

I keep getting this message when I attempt to edit one of my flows.

'Flow initialization failed. Please make sure there is an active internet connection and contact your administrator.'

Correlation Id: 081a078c-be15-4b9e-86ee-1e42f4c03d4b

Any idea what is causing this and a remedy?

Categories:

Power Automate Desktop

All responses (5)

Answers (0)

Sort by

BalamuruganDev 57 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @stevec63 ,

Is it to Desktop flow or Cloud flow?
If Desktop flow try to re install Power Automate Desktop exe again
else
Provide some reference image about the issue

Thanks,
BD
stevec63 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Desktop flow
I have done a complete uninstall and re install twice already no change.
Before :

After I select edit :
Kaif_Siddique 2,108 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @stevec63 ,

The machine that hosts Power Automate for desktop can't connect to the required domains. This issue could happen either because the domains are blocked on the network, or because you're using a proxy server that requires authentication.

Please go through Microsoft documentation to resolve this issue.
https://learn.microsoft.com/en-AU/troubleshoot/power-platform/power-automate/cannot-sign-in-create-edit-save-view-desktop-flows

let me know if this helps you to resolve this issue

Regards
Kaif
rolign on at

Like
a
(1)

Report
Copy link

Link copied!

Only thing that worked for me was importing the failing desktop flows to another environment and then exporting and importing back with a new version.
ThiagoOechsler 5 on at

Like
a
(0)

Report
Copy link

Link copied!

I am having the same error, but if this would be a network or connection issue then Power Automate would not let me create a new flow. The same error occurs on a Copy of the problematic desktop flow. So it is something with the flow itself.

Wish Power Automate had better error descriptions or at least a stack trace or something. These simplified error messages feels like things a developer would do while learning hello world.