POST tour (V2) possible regression with servicetime: 0 on duplicate-coordinate stops

API
1

Hi RouteXL team,

We’ve long used a two-call method to isolate pure travel time:

  1. Optimization call – full constraints (ready, due, etc.) with skipOptimisation: 0
  2. Travel time call – same locations but all constraints stripped and servicetime: 0 for every stop with skipOptimisation: 1.

Until sometime in 2025 most likely, the second call produced identical arrival times for consecutive stops that share coordinates (because travel time = 0 and servicetime = 0).
Now those same tests always add +5 minutes at each duplicate stop, even though we explicitly set it to 0.

Payloads to reproduce

Zero minutes servicetime

[{"name":"Amsterdam","lat":"52.3676","lng":"4.9041","servicetime":0},
 {"name":"The Hague","lat":"52.0705","lng":"4.3007","servicetime":0},
 {"name":"The Hague2","lat":"52.0705","lng":"4.3007","servicetime":0},
 {"name":"Rotterdam","lat":"51.9244","lng":"4.4777","servicetime":0},
 {"name":"Utrecht","lat":"52.0907","lng":"5.1214","servicetime":0}]

Five minutes servicetime

[{"name":"Amsterdam","lat":"52.3676","lng":"4.9041","servicetime":0},
 {"name":"The Hague","lat":"52.0705","lng":"4.3007","servicetime":5},
 {"name":"The Hague2","lat":"52.0705","lng":"4.3007","servicetime":5},
 {"name":"Rotterdam","lat":"51.9244","lng":"4.4777","servicetime":5},
 {"name":"Utrecht","lat":"52.0907","lng":"5.1214","servicetime":5}]

These two requests produce the same result.

Question:
Has the engine started overriding servicetime: 0 when two consecutive stops have identical lat/lng, or is this an unintended side-effect of a recent update?

Thanks for clarifying—this behaviour impacts our travel-time baseline workflow.

2

[Updated answer]

After investigating, we confirmed that the engine was unintentionally overriding servicetime: 0. This was a side effect of a recent server update, where servicetime: 0 was incorrectly interpreted as a missing value, defaulting to 5 minutes. We’ve addressed the issue, and the engine now respects servicetime: 0 as intended.

1 Like