Cannot create new session to execute unattended run

(0) Share

Report

Posted on by TesDA

611

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?

Categories:

Power Automate Desktop

All responses (8)

Answers (1)

Sort by

mattias1172 on at

Like
a
(1)

Report
Copy link

Link copied!

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 611 on at

Like
a
(0)

Report
Copy link

Link copied!

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

Like
a
(0)

Report
Copy link

Link copied!

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 on at

Like
a
(1)

Report
Copy link

Link copied!

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 Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

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):
Verified answer

TesDA 611 on at

Like
a
(0)

Report
Copy link

Link copied!

After alot of back and forth with our colleagues in our national dept we learned that we need a gateway
AlexScharpé 35 on at

Like
a
(1)

Report
Copy link

Link copied!

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
CParsons09 141 on at

Like
a
(0)

Report
Copy link

Link copied!

Isn't MS deprecating gateways?
Have you had any issues going after using a gateway?
We just moved our VM's from local infrastructure to Azure and getting this error sporadically. With automations running 24/7, we aren't always available to restart the flow.