Flow launch panel doesn't load

[Anonymous]

Hello,

I have an instant flow which I trigger from a Sharepoint list when an item is selected. This flow is used by about 15 users and works very well for all users but one. When this user triggers the flow, the Flow launch panel opens and stays in a loading state forever instead of offering the usual run flow button...

 Thanks for your help

[SIneichen]

I have the exact same situation on multiple environments. Users can see the flow but the panel does not load. Here is what I have found out. If a user opens https://make.powerautomate.com/ previously and selects his region, for example Switzerland, he can start the Flow from the library / item itself... Can anyone confirm this?

[JJ_H]

I found out for a number of users in my environment they had a Power BI Pro trial that had expired, and despite having Power Automate Free licensing applied directly from M365 admin centre, the expired trial was blocking access to power flows. This explains why it was happening irrespective of browser - it is definitely related to Microsoft account and Power Automate.

[IsraelRC971]

@JJ_H 

I find this very interesting. Could you elaborate further?
Why does the Power Bi licence affect PowerAutomate and SharePoint actions? I understand that, as they are Power Platform licenses, it must have something to do with it.

Best regards.

[JJ_H]

Apologies - I meant to say Power AUTOMATE Pro trial (Not BI), but the issue on the web was that any calls made to power automate whilst logged in with the account on the expired trial were being redirected to powerautomate.com/trialexpired and would just show the blank launch panel.

[JakubKolacek]

Hello everyone,

we had the same issue with two users. Logging in to https://make.powerautomate.com has solved the issue. The users had the following licenses before it stopped working:

Microsoft Power Automate Free

Office 365 E3 (Power Automate for Office 365 turned on)

Reassigning licenses didn't help, they didn't have the Power Automate Pro trial, only the login to make.powerautomate.com. However, this is really a frustrating issue.

[Crissy]

Thank so much for your help, if the user open link the flow panel load. 
Thanks again,

Cristina

[IsraelRC971]

Hello, everybody!

Unfortunately, this solution doesn't seem to work for the users reporting the problem to me.
I'm checking licenses, and AD groups, comparing users who fail with those who don't, and, if it's related to this, I'll update with a possible solution.

It's pretty frustrating, I'm not going to lie.

@JJ_H  How could I check that users are being redirected to powerautomate.com/trialexpired?
I don't see that information anywhere.

Kind regards to you all.

[JJ_H]

You can see it under browser inspect element > Network logs. It is doing a redirect and launch panel cannot load it (so shows blank). 

Also if you log into https://make.powerautomate.com as the user with the expired trial - it automatically redirects to the same trial expired link. Until you deal with that trial expiry (renew license, cancel, extend) it will not go away.

[trilogyadmin]

Wow thanks for this. It did actually work when doing this to the User who had the issue.

[Olivier_1968]

Hi, 

Many thanks for sharing. It works for me !!

[JacobCats]

Hello,

Thank you, logging in to power automate solved this for me.

[W_Rocketpilot]

I have the same issue in the environment of a customer. It worked for a couple of weeks and now the panel is loading forever. I logged in at make.powerautomate.com and checked my license, but it doesn't fix the problem. Switched between browsers, cleared cache, set a new trigger in the flow, but nothing seems to work😔.

[SIneichen]

Hey @W_Rocketpilot  Sorry to hear that. You confirm my suspicions. It used to work without a workaround. Surely there is a problem here on Microsoft's part, but they are not responding. No idea how to get this on their radar.

[W_Rocketpilot]

The problem is solved! I was a little confused about my license what looks as needed and my colleague as well. But the colleague I shared the flow with had only the Power Automate Free license. When she logged in at make.powerautomate.com there was no redirecting or something as talked about above that was why I didn't expect this was the problem. After activating the Power Automate for Office 365 license wich I had but she didn't the flow works perfect! @SIneichen maybe als for you a working solution?

[JoeFox79]

I've had this issue sooooo many times, but often by the time I have tried to find a solution via e.g., this site, the problem has gone away. It's super frustrating when it happens, and I just wish there was a root cause but no matter how hard I look, I cannot find one. The somewhat spurious reasoning that it is network related grates on me as I don't believe this is the root cause and is being used as a 'holding' excuse whilst the problem miraculously resolves itself. 

If anyone has done any advanced digging into this, or found the root cause and/or a solution then please share it here.

Thanks.

[JoeFox79]

Just to add a quick comment, this issue occurred for me today and the way I resolved it was to log out from all my sessions within the particular tenant, and then log back in. The logging out needs to be complete, so if you have e.g., a Power Automate session open in another browser/tab, then be sure to log out of that too. I'd imagine you should do the same for Teams too - properly log out of Teams rather than just closing it.

Also, to note, in the past, logging out/in didn't resolve the issue although I cannot be sure I properly logged out of all sessions in previous cases.

[Anonymous]

I am facing the above issue, in spite of being the owner of the flow. Has anybody got a solution to this yet?

[Olivier_1968]

Did you try to logon to the power automate portal ? and try again to launch your flow.

[bu11frogg]

For us, it turned out that the users experiencing this problem has enrolled themselves in a 90-day trial of Power Automate, which had then expired.  Logging into Power Automate and extending the trial immediately fixes the issue, so I've asked for IT to remove that trial license (however that works). 

[bu11frogg]

For us, it turned out that the users experiencing this problem has enrolled themselves in a 90-day trial of Power Automate, which had then expired.  Logging into Power Automate and extending the trial immediately fixes the issue, so I've asked for IT to remove that trial license (however that works).