Collections are a great way to run a high volume of Requests without coding concurrent requests logic yourself. RedCircle API allows you to start many Collections and they will be put into a queued state and executed sequentially.

By setting a priority to a Collection you can determine the order in RedCircle API executes your queued Collections. Collections with a higher priority will be executed before those with a lower priority .

By using this method you can ensure your time-critical Collections are always executed before your "background", or non time-critical Collections.

There are 5 priority levels that can be applied to a Collection, they are:

highest , high , normal , low , lowest .

The priority of a Collection can be set when you create or update the Collection. If no priority is specified when the Collection is created it will be assigned the normal priority.

Collection priority does not affect the speed that your Collections are executed, just the order. Priorities are evaluated at the point at which the platform is going to start the next Collection. For example, if you had a Collection already running with a normal priority and you started another Collection with a high priority, the platform would still complete execution of the already-running normal priority Collection before starting the newly added high priority Collection.

Collection priority cannot be changed once the Collection is in the queued or running state, so be sure to set the desired priority before starting the Collection.