We have a very large ReFramwork workflow integrated with SAP.
When it runs every 5 minutes via a trigger in orchestrator and I’m logged on to our server as User X for example, the UiPath Agent triggers the workflow accordingly and everything works as expected and I can see all the relevant SAP screen being filled, etc…
Unfortunately, everything falls apart when the workstation is locked. We’ve started addressing one issue at the time i.e. SimulateClick, and other problems but started to encounter more problems i.e. SimulateType for the TypeInto for example. As we have a lot of workflows, this will take forever to change, not to mention to re-test, so this is not a solution.
After researching this some more, we thought we’d have a solution by using the “Login Into Console”. We enabled it and tried both scenarios when set to “yes” or “no” but it still seems to be running the process as a background process (Not sure if this is correct) but I’m still getting issues with the likes of the TypeInto, etc…
I thought that when it was set to “yes”, it would end the current RDP (if any) and start a new one and the workflow would be triggered as if I had an RDP session running as User X and everything would work as expected
a) my session with User X remains opens and
b) the workflow no longer gets triggered in the foreground as it did before when the “Login to console” was disabled. When I lock the workstation on purpose to test it, it still run the workflow but as I said, in the background causing a bunch of errors!
Any reasons why my session is not being ended by orchestrator when the process is started and why the workflow appears to be running but as a background process rather than in the foreground one.
I’d appreciate any help.