Ilya Builuk
Ilya Builuk
Yes, these are the hard requirements of multi-jobs. Possible work-arounds for your use case: # Option 1: tour order - use tour order feature to have pickups ordered strictly before...
In 1.19.0 I did a big architectural change and introduced a feature concept. Features can be combined and this requires some extra change in the logic which responsible to catch...
Hi! Hard to say what is the reason: I haven't worked on the project for years.
Sorry, I missed original bug as I'm not actively working on the topic anymore. I would agree with the suggestion
Hi! Thanks for reporting it, can you make a pull request?
regular (not interval) breaks are kind of soft. However, if you're saying that statistic shows breaks time without break activity, that looks strange. It requires some investigation (but I'm not...
Sorry, need more time to reply
Thanks for reporting! I can confirm the issue: there is an overflow happens in activity place schedule times. I would need to find time to dig into it to understand...
Basically, the reason is that you're using required break feature which is kind of experimental: ```json "breaks": [ { "time": { "earliest": "2025-02-10T12:00:00.000Z", "latest": "2025-02-10T12:00:00.000Z" }, "duration": 300 } ]...
Hi, built-in objectives for reducing overlap are highly experimental. You can develop your own model for your use case by extending the solver when using it as library (not through...