The length member of TimeWindow class defined here:

is initialised here:

Due to both start and end members being shadowed by start and end arguments, the computed length value is based on UserDuration instead of Duration.

At the moment it is not a big deal, because TimeWindow::length is used only in vehicle comparison:

, which works correctly whether or not the value is scaled, and in job: , where it is used to initialise Job::tw_length, which itself is not used anywhere and gets removed in #1014.

Anyway, to avoid any possible confusion in the future, I would propose to either scale the value: length(utils::scale_from_user_duration(end - start)) or add a length() member function and compute the value on the fly.