Is it by designed that it is limited to 2 jobs when requesting a Job via API - StartJob. Because we experienced that when there are already 2 jobs requested(1 ongoing ,1 on queue), succeeding requests will be ignored.
It is by default that you cant have more than one job on the same robot in pending state, as per it would have no use to have it…
You can only schedule the same Job/Process twice one while in progress and one in pending. If the Job/Process is different I believe you can have 3 pending jobs when triggered for an Specific Robot.
Allocating dynamically I think you have more leeway.
I see, so it is behaving as designed. Many thanks.
This is a good way. However, we have outdated Orchestrator that don’t have such feature yet.
Oldest I’ve used is 2018 which has the dynamic allocation, how old are we talking here?!