1. What happens if a new job is triggered while the robot it is assigned to is executing a different process?
View Answer
The new job is left in a ‘Pending’ state until the robot finishes executing the process. The new job is executed as soon as the robot becomes available
2.
Is it possible to check whether a Robot that is connected to Orchestrator is available or not in real time?
View Answer
Yes, this is possible through the Heartbeat mechanism; the status of each robot is updated on the Robots page
3. Is it possible to reprocess a transaction in a Queue after its failure due to an application exception?
View Answer
Yes, if the Auto-Retry property of the Queue is enabled
Yes, it can be retried manually on the Transactions page
4. How are Robot Keys generated?
View Answer
Orchestrator generates unique Robot Keys during the robot provisioning process
5.
Is using the ‘Publish’ button in Studio the only way to upload a package to Orchestrator?
View Answer
No. Packages can also be published via the Packages page in Orchestrator
