Duplicate addresses not visited together

request.json (49.5 KB)


We’re currently experiencing an issue where a duplicate address is not always visited at the same time. For example in the request we’ve attached “6 damascus drive” is visited twice, but “35 Hun cres” is visited in between them. We recently saw this issue with duplicate addresses being split between multiple vehicles, which is why we’ve added the “in_same_route” relations to the example request.

Thank you for your example. That can indeed still happen sometimes. We are currently working on a solution that we will probably roll out in the next weeks. Then this should not happen anymore (or become much rarer).

1 Like


Just wondering if the solution you mentioned has been rolled out now? We saw the issue crop up again in a job a few hours ago (702e8dc4-017a-4466-981c-8b8e1690a4f9). But it looks when we try to run the same request again it doesn’t happen. I’m assuming it’s just a coincidence, but thought I’d mention it.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.