If you are trying to use RPA Central to schedule a botflow on another machine you will need to make sure that you are logged out of the machine you are unlocking for RPA to interact with it. Unlike previous versions, you cannot stay logged in.
For Nintex RPA versions from 16.5.1 and higher, first check to make sure you have the correct version of Unlocker which has the version 16.5.1.
You may not receive an error, the bot may go into offline status or you could receive an error saying Target not Found.
To run a botflow unattended, you must change the settings on RPA to run as Administrator. To do this:
Use a batch file to disconnect the user so that RPA can interact with the machine. The Unlocker Action will have the credentials set up inside it to log in to the machine to run the botflow.
Here is the batch file used to disconnect your VM:
Go to Notepad and copy the batch file from the document
for /f "skip=1 tokens=3" %%s in ('query user %USERNAME%') do (
%windir%\System32\tscon.exe %%s /dest:console
Save as .bat and save to desktop so you can find it.
If scheduling a botflow that has to access an RDP and RPA Central is on another workstation or server, you can schedule a botflow that would run the batch file above right before it. Then run the original botflow. Or you can manually use the batch file right before you schedule the botflow in RPA Central.
Unlock Action Help - There is a collapsed section named "Handling RDP" toward the bottom.