Job creation in sandbox failing with "No geojson available for london" error

Bug Reporting
1

All of our automated Stuart tests have recently started failing due to all job creation requests returning a 500 “UNKNOWN” error with the error message reading “No geojson available for london”.

Here is a sample job request payload:

{
    "job":
    {
        "pickup_at": null,
        "dropoff_at": null,
        "assignment_code": "test_assignment_code",
        "transport_type": null,
        "pickups":
        [
            {
                "address": "2 Tulse Hill, London SW2 2TP, UK",
                "coordinates":
                {
                    "lat": 51.454777,
                    "long": -0.113982
                },
                "comment": "Pick me up",
                "contact":
                {
                    "company": "Courier Hub STRTS",
                    "firstname": "Courier Hub Contact",
                    "lastname": null,
                    "phone": "+1 833-467-9651",
                    "email": null
                },
                "access_codes": null
            }
        ],
        "dropoffs":
        [
            {
                "package_type": "medium",
                "package_description": "Deliver me",
                "client_reference": "test_client_reference_postman",
                "address": "1 Montego Close Railton Road, London SE24 0LH, UK",
                "coordinates":
                {
                    "lat": 51.458803,
                    "long": -0.109983
                },
                "comment": null,
                "contact":
                {
                    "company": "Test Company",
                    "firstname": "Test Recipient",
                    "lastname": null,
                    "phone": "+1 971-222-9641",
                    "email": null
                },
                "access_codes": null
            }
        ]
    }
}

It looks like the errors start some time between Friday and today. There have been no changes on our end in the intervening period.

2

Hi Mirek,

Thank you for letting us know. We are currently investigating the issue and let you know as soon as a fix has been implemented.

Kind regards,

1 Like
3

Hi Mirek,

The issue should be resolved now, can you please check form your side and let me know in case you are still experiencing errors?

Kind regards,

Deborah

4

Hi @d.hediger, things have been working as expected since last Tuesday (May 16th), thanks for closing the loop!