Setting "Run only one job at a time" not applied

News Knowledge Base
,
1

Why are jobs not starting with different Account-Machine pairs?

Issue Description

When a high volume of items is added to a Queue Trigger and multiple Account-Machine pairs are needed, Orchestrator attempts to start multiple instances of the process with the same Account-Machine pair, leading to failure. The option "Run only one job at a time" is already checked.

Root Cause

The flag for the "Run only one job at a time" option is sometimes not correctly being read from the database.

Resolution

  1. Uncheck the option "Run only one job at a time" for all Robots used
  2. Save the modifications
  3. Check the option back to re-enable it
  4. Save the settings once more

Changing the setting back forces a database "refresh" so it is correctly interpreted.