If your robot machine is not connected to your orchestrator instance the only way to run the robot is by using Windows Task Scheduler.
You will need to make the a trigger in Task Scheduler which will run every minute or as per your needs.
Two things you will miss with this approach
With this approach the robot execution logs will never be sent to Orchestrator so there is no way of knowing if the robot executed as required.
You cannot access any credentials or assets stored in orchestrator. So all of these need to be accessible to the air gaped robot.
The robot execution logs will be available in the robot client alone. You will need to analyze the logs using splunk forwarder or elastic search. But you cross the bridge when you get there.
For now Windows Task Scheduler should run your robot. I have a previous post on how to do this.
You can write a simple bat file with the following contents and save it to your desired location.
“FullPathToYourUIROBOTEXE\UiRobot.exe” execute --file “FullPathToYourProcessXAMLfile\Main.xaml”
The quotes are important as some paths may have spaces which bat files do not allow.
In your Task Scheduler in windows you can create a basic task
Click ok in the first window after checking on the yellow marker. This ensures that UiRobot.exe has the required access le…
Hope this helps.