Answered

Need help with update error: Error occurred while communicating with the cloud services.

(2) Share

Report

Posted on by User1314

It was working completely fine until I updated Power Automate Desktop and then encountered this error. I tried researching online and tried different things but nothing seemed to work. I uninstalled it and removed it from all sources (program files, appdata etc.) reinstalled it and then encountered the exact same error. Does anyone have any ideas on how to fix this? I would really appreciate some help!

Categories:

Power Automate Desktop

I have the same question (4)

All responses (16)

Answers (1)

v-xiaochen-msft on at

Like (0)

Report

Hi @User1314 ,

Please take a look at this documentation.

https://learn.microsoft.com/en-US/troubleshoot/power-platform/power-automate/cannot-sign-in-create-edit-save-view-desktop-flows

Will it help you?

Best Regards,

Wearsky

Was this reply helpful? Yes No
User1314 17 on at

Like (0)

Report

Thank you for reaching out but it's not a sign in error. I can sign on but as it is loading the environment it prompts the error shown above. The application also worked well until I updated it to the newer version.

Was this reply helpful? Yes No
ksdgfbiwebfkeqb 9 on at

Like (0)

Report

I have exactly the same problem, since upgrading this morning to build 2.28 January 2023 update of Power Automate for desktop | Power Automate Blog (microsoft.com) v2.28.267.23013. "An Error occurred while communicating with the cloud services. Make sure that access to the required cloud services aren't blocked and try again"
I changed the registry setting to disable the new certificate check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Power Automate Desktop\DisableCheckCertificateRevocationList=1 but that didn't help. I have another computer on the same subnet I have not updated yet, it's still on v2.22.00205.22189 and it runs perfectly, I'm declining the update on that computer until this error can be resolved. I have not found any release notes online about changes to URLs etc. in this build that could be causing the error.

Was this reply helpful? Yes No
User1314 17 on at

Like (0)

Report

Yeah unfortunately I lost all my flows due to this. I never expected an update to cause this, I am stuck because the re-installation didn't work.

Was this reply helpful? Yes No
ksdgfbiwebfkeqb 9 on at

Like (0)

Report

Uninstall Power Automate Desktop then download this installer for the previous build https://go.microsoft.com/fwlink/?linkid=2102613 from December 2022 update of Power Automate for desktop | Power Automate Blog (microsoft.com) and you should be back up and running. It just worked for me. Hope there's more info for a real fix soon.

Was this reply helpful? Yes No
User1314 17 on at

Like (0)

Report

Oh interesting, I was thinking about trying to re-install an older version. I just gave it a shot but unfortunately it didn't work. I even tried the November 2022 link too but for some reason it just keeps giving the same error. I suppose I will have to wait until they either fix this or a new version is released and hope for the best. Unless there is some other option.

Was this reply helpful? Yes No
ksdgfbiwebfkeqb 9 on at

Like (0)

Report

When you reinstall there’s a list of checkmarks about what components you want to install. I selected everything except the 2nd from the bottom, something about additional data collection. On that screen try unchecking the option for the Machine Runtime that allows connections from the cloud portal, I can’t recall the exact wording now but it’s near the top. Maybe without that Portal connection component it will work.

Was this reply helpful? Yes No
User1314 17 on at

Like (0)

Report

Yeah! I had the same thought! I tried unchecking that one and there is another box that is slightly similar and I unchecked that as well but unfortunately no luck. I thought for sure it would work, it's a very strange error.

Was this reply helpful? Yes No
pm7158 10 on at

Like (0)

Report

I lost all my flows as well.

Was this reply helpful? Yes No
Ciaran 261 on at

Like (0)

Report

I have the same error. I have tried all the solutions listed on forum but to no avail. I have just raised a ticket with Microsoft and await their response. If I receive anything back i will gladly share it

Was this reply helpful? Yes No