Cannot create new session to execute unattended run

[TesDA]

I've looked through all of the current posts on this and they didnt help. 

We are using a service account on an Azure Virtual Desktop using a machine (not a gateway). 

The Service Account does have a Power Automate license and and we have an unattended license for the environment it is using. 

The machine is showing as connected, so I know the virtual desktop is online and running power automate when no one is logged on. 

What could be going on? 

[mattias1172]

What is the exact error you are getting?

Also, to be sure, no one is logged in at the same time the flow tries to connect? If your running windows 10/11, only 1 logged in user at a time is supported. 

[TesDA]

@mattias1172  We're running Windows Server 2016 Datacenter. Does it need to be a later version of Windows Server?

[TesDA]

I just checked the docs and it looks like Power Automate Desktop supports Windows Server 2016 Datacenter however that might be outdated. https://docs.microsoft.com/en-us/power-automate/desktop-flows/setup

[mattias1172]

If the VM matches the prerequisites, try setting up power automate runtime on another computer and running the unattended flow on that. This will being to shorten our potential problems. 

 

[elaaboum]

Hi @TesDA ,

could you share the runId of the unattended run that failed with that error. (see screenshot below for how to get that runId):

[TesDA · Accepted solution]

After alot of back and forth with our colleagues in our national dept we learned that we need a gateway

[AlexScharpé]

Hello,

Experiencing the same issues here, wouldn't know how to solve as I bump on this error quite inconsistently.

Here's a runID of my unattended run:

Any idea how this issue could be resolved?

Kind regards,

Alex