As announced for v1.27.0 there is a now an additional "exit" feature given via the settings.maximumStagnationDuration : integer <int32> [ 1 .. 86400 ] Defines the maximum duration (in seconds) the optimization may continue without improving the best-known solution. If no better solution is found ...
I have analyzed all the rules. Some of them are already fullfilled with the restrictions in the API. Finally, I've improved the documentation of the Driver's Working Hours. I wrote all the restrictions for xRoute. Here they are:
Route Optimization OptiFlow API 1.27.0 FEATURE 08.10.2025 Added support for early termination via maximumStagnationDuration, allowing optimizations to stop if no better solution is found within a specified time window.
I forwarded youre last response to Yann who will look into this in the next days.
He requires some time for a proper reaction but he promised to return to your task...
Here's one aspect you should be aware of if you want to apply the "respectedSequences" on more than 200 orders:
A single respectedSequences element is restricted to a maximum of 200 order categories. Imagine you tried to compensate this limit by concatenating 2 respectedSequences via ...
Route Optimization OptiFlow API 1.26.0 FEATURE 07.10.2025 Added overloads to define an extra cost for loading orders onto a vehicle when the vehicle's load exceeds a threshold.
Route Optimization OptiFlow API 1.26.0 FEATURE 07.10.2025 Added an ...
For the 2nd part of the question: There are plenty of rules that are defined to be sure that the tourRestrictions parameters are consistent. One of them is that, maximumDrivingTimeBetweenDailyRests ≤ maximumTravelTimeBetweenDailyRests + dailyRestTime. With your test, an exception ...