Scheduler executes on already running robots even when there is other available robots

orchestrator
robot

#1

When the scheduler on the orchestrator executes, it often queues up a job on already running robots, instead of taking one of the currently available ones.

We currently have a support ticket in progress on this issue. But i wanted to hear whether anyone in the community has had this issue, and how you remedied this?