Note When you start a robot through Java/.Net API or as a RESTful service and the Management Console does not have enough slots to run it, a message appears that no slots are available. The robot is not queued. Therefore, when you start a robot using API, create a way to schedule robots such that they can always run when there are enough slots. For example, you can keep a count of the number of running robots and start a new robot only when enough slots are available, or you can have loops that attempt to run a robot and if the lack of slots prevents it from running, the loop should wait and try again.