I have windows server 2019 installed physical machine that runs a few desktop flows unattended.
My flows actually runs smoothly with unattended condition but if Windows Server runs more than approximately 48 hours suddenly my flows fail to run with the error "Cannot create new session to execute unattended run."
If I re-start the server everything goes back to normal. So all my flows run unattended as expected.
After I start to get this error for my flows, sometimes a flow is able to run and sometimes is not. I mean the same flow can be failed but next time the same failed flow to be run without any problems.
As I said, restarting machine solves this problem.
By the way; the same flows can be run attended although it is impossible to run them unattended.
Any help appreciated.
We have a similar problem but even a reboot hasn't brought things back to working. Did you ever find a root cause?
Are you still facing that issue ? If yes, could you provide the run Id as shown below ?
I just got this issue as well. I'm just here for the solution
It turned out in my case, after trying all sorts of things including updating to latest version of everything and creating new everything that the fundamental issue was that my IT department put DUO login security on the machine, which of course stops unattended flows in their tracks because they can't log in.
No solution that I'm aware of. Either have to use a tool that is DUO aware or remove DUO.
Hi belzinga,
could you provide the run id (see my comments above on how to get it).
We do not support Multi Factor Authentication + in case an extra authentication step is required to RDP to the machine, the unattended runs are expected, currently, to fail !
Ooops. I deleted the flow.
If you got the issue again, please share the runI d here or send it to me as private message !