Limit the number of concurrent and queued instances of a process
We need to be able to limit not only the instances of a process that run concurrently, but also the instances of a process that get queued.
For example, if Process A is scheduled/triggered and Process A is triggered once more, while Process A is already in the Queue/Running mode, it should neither start nor get queued. The same goes off if we have the same case for Process B, C, D etc.
Moreover, the process should pick only one robot from the pool so that it is not started from both (in our case the pool consists of two Solobots).
“- This post was created by the Softomotive Support Team. Thank you Stig Kølbæk for the suggestion!”