Live Service Requests returning a 500 internal server error
Closed this issue · 1 comments
dave-t-c commented
When requesting live service information for a stop, a 500 status code is returned.
Example
Request:
curl -X GET "https://localhost:5001/api/services/ASH" -H "accept: application/json"
Response:
{
"type": "https://tools.ietf.org/html/rfc7231#section-6.6.1",
"title": "An error occurred while processing your request.",
"status": 500,
"traceId": "00-64c29a3e173073d9a5be5a1bd8e42746-3ca0d124da04b2c1-00"
}
This appears to be being caused the service request, as it is failing on
response.EnsureSuccessStatusCode();
which suggests this may be being caused by the request to the TfGM open data API.
dave-t-c commented
This appears to be a problem with the IDs being used for stop requests, as the IDs appear to have changed.
For example, the IDs for Ashton (ASH) have changed from [783, 784, 785, 786]
to [1059, 1060, 1061, 1062]
.