Not able to export, import MS Flow, Not able to open Connections

[vermaaman]

Hello, 

I have created a flow which is being triggered by PowerApps. I got some connection issue so thought to export the flow, then delete it and import it which might fix my issue. when i click on export button the wheel started spinning and never ends, then i changed my browser, that also didn't help, after that i though the problem is only with this flow, so to ensure i tried with other flows and surprisingly they are also facing the same issues.

I tried opening connection but couldn't open connections as well.

I am using a service account which is having E3 license assigned to it. Not sure why is the issue can anyone help? 

[v-litu-msft]

Hi @vermaaman,

It seems like a temporary issue, do you still have the problem with the Power Automate pannel?

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Dowsetts101]

Did you ever get a resolution on this issue. This has started happening to one of my accounts as well.

[JPMontoya]

I am currently facing the exact same problem, and at a very inopportune time as well, I must say. Has this turned out to be actually temporary or do I now have the pleasure of redoing the flows manually in the new environment?

Curiously enough, I am able to export Custom Connectors and PowerApps without any problems whatsover. I can also look at the Connections in the PowerApps Webclient, but not in PowerAutomate.

I am trying to create exports in the default environment of the given tenant, in case that helps identifying the problem.

[peter_86]

I was shocked, shocked I say, to find the page did not work in Chrome (8 attempts) but it loaded instantly in Edge.

[JPMontoya]

so, just to report back on this.

In my case, it happened to be temporary. I had the issue for both the account that was supposed to export, as well as for the account that was supposed to import in the new environment.

The next day, things were back to normal, so I guess it really is just an annoyance. I did also manage to sort of get a "workaround" for this. If you have access to multiple accounts in the same environment, you can share whatever you wish to export with another account you have access to and then perform the export on that account. Not sure I would to that for importing as well though, as there seems to be sort of a fixed initial owner that can't be removed, at least not from what I've seen.