A scenario could exist where multiple optimization requests are generated for shipments with compatible characteristics. This might occur if similar requests are initiated by different users operating on different load plans.
In an environment that supports multiple Optimizers, two or more of these compatible optimization requests could be processed concurrently. Once a load, trip or booking is assigned to a given optimization request, it will not be available for consideration by any other request until processing for the first request concludes. In this scenario, compatible shipment legs might be assigned to two different loads because there was no visibility to the other transactions. If the requests were to be processed serially, a load created by the first request would likely be amended to include an additional shipment leg when processing is subsequently performed for the second request.
A global setting controls whether optimization requests with the same characteristics will be allowed to be processed concurrently. If the setting for the Allow Concurrent Processing for Optimization Requests flag is False, the process used to select the next optimizer request for processing will determine if the load, trip and booking filter criteria associated with the requests are equal, and if so, processing for the request will be deferred until the optimization for the conflicting request is completed. Optimization could be performed for other non-conflicting requests in the interim.