When you activate a clustering the new clustered loops are created with different work address

[sync-by-unito[bot]]

When you activate a clustering in the organisation dashboard the newly clustered loops are created with a work address that is different from the company's address configured in the settings. The address that is configured on the loops by the auto clustering is Thembelihle Street, City of Cape Town, Western Cape 7941, South Africa

We need to investigate this. One of our new clients experienced this issue where the company address on settings was changed to the one above. This could have a huge impact on billing and distance might not match the actual distance.

┆Issue is synchronized with this Clickup task by Unito

[sync-by-unito[bot]]

➤ Edmore Mandikiyana commented:

Waiting for a response from @Xabiso Nodada

[sync-by-unito[bot]]

➤ Edmore Mandikiyana commented:

I see that page hasn't yet been updated to send the complete address to the API though. @Xabiso Nodada I doubt this is still an issue in production. I have one question though. Should we use the work address for the commuter or the organisation's address when creating these loops? We currently use the commuter's work address. Also, the payload is missing province. @Jonathan Ngbonga comment please, i know you were working on this at some point, so we can reduce the no. of API calls to the Map service provider.

[sync-by-unito[bot]]

➤ Edmore Mandikiyana commented:

This loop was created manually, so the issue has nothing to do with auto clustering. I however cannot reproduce it but i suspect it might have been caused by API geocoding address because it was incomplete, then multiple matches get returned, after which it picks the first one.

[sync-by-unito[bot]]

➤ Xabiso Nodada commented:

@Edmore Mandikiyana has this not been resolved. I remember you we working something similar? Or was it a discussion