We are testing two very close addresses:
but the API is returning 400 Bad request with a ROUTE_NOT_VALID code.
I tested it on the Stuart dashboard and it returned the same problem.
NOTE: The same thing happens with addresses that are further from each other, such as:
Hi Artur,
Thank you for raising this and the clear example provided - we will investigate and get back to you as soon as we can.
Kind Regards,
Hi again @Artur
We have discovered a bug behind one of our Sandbox features. We have disabled this while we investigate so you should be able to carry on with Sandbox job creations as normal.
Let us know if you experience any further problems.
Kind Regards,
James
Hi! Any chance this bug is present in production too? We are seeing an issue in production where we are receiving a CANT_GEOCODE_ADDRESS error message on a job with two addresses that seem to be perfectly valid in sandbox.
Here’s the json for the job in question:
{
“job”:{
“pickup_at”:“2021-05-31T14:44:16.000000+0200”,
“pickups”:[
{
“address”:“Calle Francisco de Rojas, 7, 28010, Madrid”,
“comment”:"",
“contact”:{
“firstname”:null,
“lastname”:null,
“phone”:“612345678”,
“email”:null,
“company”:“Some comp”
}
}
],
“dropoffs”:[
{
“address”:“Calle de Felipe Campos, 7, 28002 Madrid, Spain 28002 Madrid”,
“comment”:“2f”,
“contact”:{
“firstname”:“John”,
“lastname”:“Smith”,
“phone”:“687654321”,
“email”:null,
“company”:null
},
“package_type”:“small”,
“package_description”:null,
“client_reference”:"",
“end_customer_time_window_start”:null,
“end_customer_time_window_end”:null
}
]
}
}
Hello,
Thank you for your message.
We could reproduce the discrepancy of both environments and we’re looking to the source of the issue.
We will get back to you with further information about it.
Cheers
Hi, have you been able to make any progress on this issue?
Thank you.
