Power Platform Community Forum Thread Details

Hi everyone,

I hope you are doing well. I am fairly new to Power Automate and while I have been very impressed by its capabilities I did run into an issue today which I could not seem to resolve on my own. Whenever I try to run a very simple test flow (e.g. launch Excel and wait 10 seconds) with picture-in-picture mode enabled it does not seem to work and a dialog box with the following message pops up: 'The "Power Automate picture-in-picture service" is not running on the target picture-in-picture session. Do you want to sign out of the picture-in-picture session and sign in again?'. When I click yes the picture-in-picture window pops up but it just tries to connect to picture-in-picture for a couple of seconds and closes afterwards with nothing happening. After this the flow ends. When I run my flow in picture-in-picture mode directly within the flow I also get an error with the following Correlation Id: 384935c0-56b2-41cb-a669-35b8fcdfdca0.

Things I have been taking into consideration so far:

I am using a Power Automate account with a premium subscription
I have checked the checkbox to enable picture-in-picture mode in the installation wizard.
I have checked and I am currently running Windows 10 Pro
I have done a simple restart of my pc 2 times to check but the problem persists
The microsoft account that is signed into my pc is different than the microsoft account I use to log into Power Automate (personal Microsoft account vs. business account to be able to use premium), maybe this is what is causing the issue but I don't know.

If anyone would be able to offer some advice or further guidance as to what might be causing picture-in-picture mode to not work on my pc it would be hugely appreciated since being able to run Power Automate with picture-in-picture mode seems like a very good tool to have. Hope you all have a nice day!

EDIT: I have also uninstalled my Power Automate and reinstalled it to be sure that the enable picture-in-picture checkbox is properly checked, but this also didn't resolve my issue unfortunately.