We have a Desktop flow which is triggered via Cloud flow in an unattended mode. Currently we are facing an error in Launch Chrome action (Problem while executing action 'LaunchChromeCloseDialog'. Failed to assume control of Chrome (Internal error or communication failure). This same problem is coming in every flow which has the Launch Chrome action. We have also tried using the Launch Edge action, but it resulted the same.
Things were working fine earlier but from past few days we are seeing this weird issue.
Also, we have noticed that there are several other flows are failing with a statement something like “waiting in queue”. We think this could possibly be due to the above flow getting stuck in some step and taking longer then the waiting time of other flows in queue but we are not getting any possible solution for these issues.
Currently we have Power Automate desktop setup on Windows Server 2019.
For the fixes we have tried below blogs but none of the solutions worked for us.
https://learn.microsoft.com/en-us/previous-versions/troubleshoot/winautomation/support-tips/web-automation/failed-to-assume-control-of-chrome-at-launch-new-chrome-action
https://www.bigmountainanalytics.com/how-to-fix-the-failed-to-assume-control-of-chrome-error-in-power-automate-desktop/
Seems like all the settings and configurations are similar as suggested.
Kindly suggest some solution as this issue is now getting critical.
Thanks in Advance
Aakash Rajput
