Hi.
So I recently dabbled a bit with the Reuse Session machine setting, but I can't seem to get it to work.
The setting is enabled, and I am able to start a flow. The computer logs in and I can see a session is created.
The Unattended flow runs fine and finishes correctly.
When I then initiate the second Unattended flow, it fails on the first UI Dependent action, as if the Session is not active.
In my test I first run a flow that logs into a website and leaves the site open.
This runs as expected (See picture)
The 2nd flow takes a screenshot of the desktop - and this fails with error:
Problem while executing action 'TakeScreenshotAndSaveToFile'. Failed to take screenshot.
Verified that the flow works in normal circumstances, so it's not an error in the flow, and the first non-User dependent actions works fine. (Get Environment variable and get datetime)
I can do a remote session to the Server after the failure and I can see that the website from the first flow is still displaying correctly as logged in.
Looking at the Sessions in PS, I can see the first Session being created and called rdp-tcp#0
But once the second flow is run, the Session changes name briefly to rdp-tcp#1 and shortly thereafter, the Sessionname goes blank (When the 2nd flow fails)
Attempts at running subsequent flows after this also fails as soon as a User dependent action is reached (See picture)
Does anyone have any experience with the Reuse Session setting and can maybe shed some light on what might be wrong?
For reference, we are running Unattended flows on a Server environment.
I suspect that MFA might be the contributing factor to why the flow fails, as we are usually approving each Unattended flow using Duo Authentication. Our hope was the Reuse Session would be able to get around the Duo requirements for each Unattended flow.
