Unanswered

Error returned: "Cannot create new session to execute unattended run." while executing a Desktop Flow using Service account in Azure VM (windows 10)

(0) Share

Report

Posted on by virendervrm

I have a Azure VM, where few Desktop Flows are executing in unattended mode. There is service account created and it has the license with unattended mode. But when we execute it it shows below error. Error returned: "Cannot create new session to execute unattended run."

Below is the RUN ID for the same. Any help is appreciated.

"x-ms-run-id": "1883e988-edd1-ec11-a7b5-000d3abb49da",

Categories:

Power Automate Desktop

I have the same question (0)

All responses (6)

Answers (0)

Sort by

elaaboum Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @virendervrm , I have sent you a private message.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Same problem here, what is the solution ?

Was this reply helpful? Yes No
elaaboum Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

@Anonymous, could you provide the "x-ms-run-id" as shown in the screenshot below ?

Was this reply helpful? Yes No
Nikola_Colic 29 on at

Like
a
(0)

Report
Copy link

Link copied!

Occasionally this happens with my flow too, and if I resubmit it, it works. I don't know how to troubleshoot it. Did you manage to get any kind of solution for this?

@elaaboum here is my x-ms-run-id: "89ffc9b5-39b7-ed11-83ff-000d3adf7523"

Was this reply helpful? Yes No
elaaboum Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Nikola_Colic,
In your case, you are getting the error code: SessionCreationTimeout. This means that PAD was not able to create Windows session needed for unattended run within 3 minutes. You can try to increase this timeout duration by setting a key in your registry:
- Path for the new key: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Power Automate Desktop\Service
- Key: SessionCreationTimeoutSeconds of type DWORD
- Value: try 300 (5 minutes) (the default value when this key is not set is 3 minutes)

After you set that value, you need to restart Power Automate Service.

see Desktop flow fails with SessionCreationTimeout error code - Power Automate | Microsoft Learn

Was this reply helpful? Yes No
Nikola_Colic 29 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @elaaboum ,
Thank you for your response. I've added new key in registry and hopefully it will fix our problem.
Link you provided was helpful, too. Just be aware that registry key name should be SessionCreationTimeoutSeconds.

Was this reply helpful? Yes No