api returns with timeout error RRS feed

  • Question

  • I am getting timeout errors returned from the api.

    Here is an example with api key removed:<key>&wayPoint.1=44.2622071,-88.411455&wayPoint.2=43.024121,-83.6769593&routeAttributes=routeSummariesOnly


    {"authenticationResultCode":"ValidCredentials","brandLogoUri":"http:\/\/\/Branding\/logo_powered_by.png","copyright":"Copyright © 2018 Microsoft and its suppliers. All rights reserved. This API cannot be accessed and the content and any results may not be used, reproduced or transmitted in any manner without express written permission from Microsoft Corporation.","errors":[{"errorCode":"","errorDetails":["Timeout occurred."]}],"resourceSets":[],"statusCode":200,"statusDescription":"Timeout occurred.","traceId":"e4e056f835cf41ebbdaf6ae231f2f14c|CO333F3B5A|"}

    Wednesday, July 25, 2018 7:26 PM

All replies

  • Hi Ethan,

    The team has investigated this issue and discovered that the time cost for the particular route is longer than 10 seconds.  They  suggest using async request to work around the issue while they continue to investigate faster approaches. FYI, for the route used in this sample, the start and end locations are separated by the great lakes so the current calculation takes around 12 seconds to finish. 



    Friday, July 27, 2018 7:25 PM