Note: As described in the article, the current way to achieve this is using min-max. It minimizes the longest route but doesn’t care much about the balance of all other routes. The original intention of min-max was exactly this, however, there are too many examples where it doesn’t work properly. Customer feedback has shown that actually nobody cares about minimizing the longest route — almost everybody cares about balancing the entire workload across all routes. Therefore, we introduced this new balance objective and expect that min-max will disappear over time.
This is still a beta feature. If you find anything unexpected or an edge case where it doesn’t work, please let us know — we’re pretty sure we’ll be able to cover that as well.