Priorities

batch priorities batches are a great way to run a high volume of searches without coding concurrent requests logic yourself scale serp allows you to start https //docs trajectdata com/scaleserp/batches api/batches/start many batches and they will be put into a queued state and executed sequentially by setting a priority to a batch you can determine the order in scale serp executes your queued batches batches with a higher priority will be executed before those with a lower priority by using this method you can ensure your time critical batches are always executed before your "background", or non time critical batches there are 5 priority levels that can be applied to a batch, they are highest , high , normal , low , lowest the priority of a batch can be set when you create https //docs trajectdata com/scaleserp/batches api/batches/create or update https //docs trajectdata com/scaleserp/batches api/batches/update the batch if no priority is specified when the batch is created it will be assigned the normal priority batch priority does not affect the speed that your batches are executed, just the order priorities are evaluated at the point at which the platform is going to start the next batch for example, if you had a batch already running with a normal priority and you started another batch with a high priority, the platform would still complete execution of the already running normal priority batch before starting the newly added high priority batch batch priority cannot be changed once the batch is in the queued or running state, so be sure to set the desired priority before starting https //docs trajectdata com/scaleserp/batches api/batches/start the batch