I am just wondering how the bot runs in production under locked screen ?
In my physical machine I have developed the code and from Development orchestrator the bot is running fine while the screen is unlocked
However I ran the bot when the screen was locked and it started getting selector issues !!
Cannot bring target application to the foreground…
For that activity I run with the property background enabled and it ran fine !!
Please provide your inputs since I want to replicate the prod environment run time in development
in unattended scenario the robot is installed in service mode and also it is not that it runs under locked screen but the robot will login and then run the automation
but in attended/development scenario first the robot is in user mode which does not support locked screen running as it would acquire user session to run the automation and if the screen is locked that means user session is not available and it would fail
Hope this clarifies
cheers
1 Like