Problems with /Line/Timetable

Here are some intial problems I have found with this set of calls. I am using /Line/Route (no parameters) to generate a list of line/originating stop/direction entries and then iterating through that set.

First off, a repeat of a comment that’s been made elsewhere in the forum. The optional direction parameter is necessary for disambiguation in a number of cases but is totally undocumented in Swagger.

Next, all rail-related calls (including london-overground and tfl-rail) return a set where the stations and stops sections are populated, but the timetable section isn’t. The statusErrorMessage for all of these is ‘The stop you selected has now been removed from the route, and therefore we cannot show you a timetable. The route page will be updated shortly to reflect these changes.’

The same problem occurs with the following bus routes:

  • 75/490001177Z/outbound
  • 75/490006706C13/inbound
  • 434/40004410113A/inbound
  • e11/490007441H/outbound

There are two rail sections that fail ‘HTTP error 400 Bad Request’, these are:

  • cross-country/0000BRSTLTM1/inbound
  • south-western-railway/0000BKNHRST1/outbound
    It looks to me as if you are including the TIPLOC suffix as part of the code and then failing to translate it to a NAPTAN code.

The following entries fail ‘HTTP error 500 Internal Server Error’:

  • 139/490000087GF/outbound
  • e1/490007441H/outbound
  • n53/490019475P/inbound
  • r7/490005081Z/outbound

There are also a number of entries where the originator, derived from /Line/Route does not match the departureStopId in the timetable, these are:

  • 24/490015832E/outbound departure stop 490011003E does not match originator
  • 40/490006232W1/outbound departure stop 490015428N does not match originator
  • 108/490018554E1/outbound departure stop 490018554E does not match originator
  • 134/490000252E/inbound departure stop 490000252X does not match originator
  • 162/490001018A/outbound departure stop 490015222D does not match originator
  • 221/490015287E/outbound departure stop 490000070A does not match originator
  • 223/490000256/inbound departure stop 490000256F does not match originator
  • 240/490015287E/inbound departure stop 490000070A does not match originator
  • 241/490013802W/inbound departure stop 490003750M does not match originator
  • 294/490007917E/outbound departure stop 490007917W does not match originator
  • 371/490018720S/outbound departure stop 490018720W does not match originator
  • 404/490005640G/outbound departure stop 490005637C does not match originator
  • 474/490013802W/outbound departure stop 490003750M does not match originator
  • 483/490015231T/outbound departure stop 490015230P does not match originator
  • b12/490012799E/inbound departure stop 490012799W does not match originator
  • k1/490007205S/inbound departure stop 490007205N does not match originator
  • n83/490015231T/inbound departure stop 490015230P does not match originator
  • n97/490013767X/inbound departure stop 490013767S does not match originator
  • r5/490007494PA/inbound departure stop 490007494DC does not match originator
  • r10/490007494PA/inbound departure stop 490007494DC does not match originator
    In most cases the departure stop is the second stop shown in the corresponding /Line/Route/Sequence call (4th in the case of lines 223 & 404 and considerably later for lines B12, R5 & R10). In all cases this appears to be caused by the route having a subsequent stop in the same NAPTAN group

All these comments are based on the update dated 8/8/2019

Result of update dated 14/8/2019:

No timetable: all rail, 75, 434 as before, e11 fixed, 197/490015223C10/inbound added
Error 400: as before
Error 500: all fixed
Mismatched departure stop: as before

Additionally, hereast-shuttle/490001338Z/outbound has stations, stops and schedules, but no stationIntervals. The intervalId for all knownJourneys is -1.

Result of update dated 20/8/2019:

As last week, except hereeast-shuttle has disappeared altogether

Result of update dated 29/8/2019:

No timetable: all rail, 75, 197, 434 as before, 195/490004289C/inbound added
Error 400: thameslink/9100GCAMBNTH0/inbound
Error 500: 68/490000077E/inbound and n38/490014050D/inbound
Mismatched departure stops: as before, add
Timetable 44/490000248G/outbound departure stop 490014050R does not match originator

Result of update dated 30/8/2019 (published 2/9/2019):

No timetable: all rail and:

No route sections for 75/490001177Z/outbound
No route sections for 75/490006706C13/inbound
No route sections for 434/40004410113A/inbound

Error 400:

Error loading timetable data for thameslink/9100CAMBNTH0/outbound: ##HTTP 400 Bad Request

Error 500:

Error loading timetable data for 160/490001249F/inbound: ##HTTP 500 Internal Server Error
Error loading timetable data for e9/490007913E/inbound: ##HTTP 500 Internal Server Error
Error loading timetable data for n277/490008507N2/inbound: ##HTTP 500 Internal Server Error

Mismatched departure stops:

Timetable 24/490015832E/outbound departure stop 490011003E does not match originator
Timetable 40/490006232W1/outbound departure stop 490015428N does not match originator
Timetable 44/490000248G/outbound departure stop 490014050R does not match originator
Timetable 108/490018554E1/outbound departure stop 490018554E does not match originator
Timetable 134/490000252E/inbound departure stop 490000252X does not match originator
Timetable 162/490001018A/outbound departure stop 490015222D does not match originator
Timetable 221/490015287E/outbound departure stop 490000070A does not match originator
Timetable 223/490000256/inbound departure stop 490000256F does not match originator
Timetable 240/490015287E/inbound departure stop 490000070A does not match originator
Timetable 241/490013802W/inbound departure stop 490003750M does not match originator
Timetable 294/490007917E/outbound departure stop 490007917W does not match originator
Timetable 371/490018720S/outbound departure stop 490018720W does not match originator
Timetable 404/490005640G/outbound departure stop 490005637C does not match originator
Timetable 474/490013802W/outbound departure stop 490003750M does not match originator
Timetable 483/490015231T/outbound departure stop 490015230P does not match originator
Timetable 686/49000012262N/outbound departure stop 490012662E does not match originator
Timetable b12/490012799E/inbound departure stop 490012799W does not match originator
Timetable k1/490007205S/inbound departure stop 490007205N does not match originator
Timetable n83/490015231T/inbound departure stop 490015230P does not match originator
Timetable n97/490013767X/inbound departure stop 490013767S does not match originator
Timetable r5/490007494PA/inbound departure stop 490007494DC does not match originator
Timetable r10/490007494PA/inbound departure stop 490007494DC does not match originator

Result of update dated 3/9/2019:

No timetable:
as previous

Error 400:

Error loading timetable data for cross-country/0000BRSTLTM1/inbound: ##HTTP 400 Bad Request
Error loading timetable data for south-western-railway/0000BKNHRST1/outbound: ##HTTP 400 Bad Request

Error 500:
none

Mismatched departure stops:
as previous

No interval sets:

Timetable hereeast-shuttle/490001338Z/outbound: no interval sets

Result of update dated 6/9/2019:

No timetable: all rail, including london-overground and tfl-rail, as well as the ones shown below

Errors from my logs - note that HTTP errors are after multiple retries:

Timetable 24/490015832E/outbound departure stop 490011003E does not match originator
Timetable 40/490006232W1/outbound departure stop 490015428N does not match originator
Timetable 44/490000248G/outbound departure stop 490014050R does not match originator
Timetable 108/490018554E1/outbound departure stop 490018554E does not match originator
Timetable 134/490000252E/inbound departure stop 490000252X does not match originator
Timetable 162/490001018A/outbound departure stop 490015222D does not match originator
Timetable 221/490015287E/outbound departure stop 490000070A does not match originator
Timetable 223/490000256/inbound departure stop 490000256F does not match originator
Timetable 240/490015287E/inbound departure stop 490000070A does not match originator
Timetable 241/490013802W/inbound departure stop 490003750M does not match originator
Timetable 294/490007917E/outbound departure stop 490007917W does not match originator
Timetable 371/490018720S/outbound departure stop 490018720W does not match originator
Timetable 404/490005640G/outbound departure stop 490005637C does not match originator
Timetable 474/490013802W/outbound departure stop 490003750M does not match originator
Timetable 483/490015231T/outbound departure stop 490015230P does not match originator
Timetable 686/49000012262N/outbound departure stop 490012662E does not match originator
Timetable b12/490012799E/inbound departure stop 490012799W does not match originator
Timetable k1/490007205S/inbound departure stop 490007205N does not match originator
Timetable n83/490015231T/inbound departure stop 490015230P does not match originator
Timetable n97/490013767X/inbound departure stop 490013767S does not match originator
Timetable r5/490007494PA/inbound departure stop 490007494DC does not match originator
Timetable r10/490007494PA/inbound departure stop 490007494DC does not match originator

No route sections for 52/490014050C/outbound: The stop you selected has now been removed from the route, and therefore we cannot show you a timetable. The route page will be updated shortly to reflect these changes.
No route sections for 75/490001177Z/outbound: The stop you selected has now been removed from the route, and therefore we cannot show you a timetable. The route page will be updated shortly to reflect these changes.
No route sections for 75/490006706C13/inbound: The stop you selected has now been removed from the route, and therefore we cannot show you a timetable. The route page will be updated shortly to reflect these changes.
No route sections for 95/490012241N/outbound: The stop you selected has now been removed from the route, and therefore we cannot show you a timetable. The route page will be updated shortly to reflect these changes.
No route sections for 185/490000248YZ/inbound: The stop you selected has now been removed from the route, and therefore we cannot show you a timetable. The route page will be updated shortly to reflect these changes.
No route sections for 419/490003632BF/inbound: The stop you selected has now been removed from the route, and therefore we cannot show you a timetable. The route page will be updated shortly to reflect these changes.
No route sections for 434/40004410113A/inbound: The stop you selected has now been removed from the route, and therefore we cannot show you a timetable. The route page will be updated shortly to reflect these changes.
No route sections for westminster-passenger-service-association/930GWMR/outbound: The stop you selected has now been removed from the route, and therefore we cannot show you a timetable. The route page will be updated shortly to reflect these changes.

Error loading timetable data for cross-country/0000BRSTLTM1/inbound: ##HTTP 400 Bad Request
Error loading timetable data for south-western-railway/0000BKNHRST1/outbound: ##HTTP 400 Bad Request
Error loading timetable data for 640/490000211F/outbound: ##HTTP 500 Internal Server Error
Error loading timetable data for e8/490013259U/outbound: ##HTTP 503 Service Unavailable

Timetable hereeast-shuttle/490001338Z/outbound: no interval sets

Update dated 9/9/2019 onwards:

I’m not going to do any more weekly updates here, but will report as and when issues are fixed or new ones appear

Update dated 25/9/2019:

No interval entries: Circle, Hammersmith & City, Metropolitan/inbound

DLR/inbound: no entries for Poplar/West India Quay-Bank/Tower Gateway, Beckton-Canning Town & Canning Town-Poplar have no intermediate stops
DLR/outbound: Bank/Tower Gateway-Canary Wharf/Poplar and Poplar-Canning Town have no intermediate stops, no entries for Canning Town-Beckton
Metropolitan/outbound: only Amersham/Chesham-Rickmansworth, Chesham-Watford & Watford-Croxley

Update dated 1/10/2019:

This has fixed the problems from last week, all the other issues are still outstanding

Just a gentle reminder - lots still outstanding here

@nickp I’ve made a start and my notes on your first post are below:

Optional Swagger Direction

Already raised under SVC-3456 - it’s been sitting on the backlog for a while now and I’ll see if this can be prioritised into a development sprint.

London Overground & TfL Rail

I’m not sure why, but we’ve never had the ability to query National Rail (inc LO/TfL Rail) timetables using the timetable API we have in the Journey Planner. I’ll take a look into if this is possible. However, it may be some time before we can expose this via the Unified API.

Buses - Stop removed from route
75/490001177Z/outbound - appears fixed
75/490006706C13/inbound - appears fixed
434/40004410113A/inbound - seems like there is a mismatch in the data provided by Surrey County Council to the NaPTAN and the data provided by TfL Surface Transport. We will investigate under SVC-6890
e11/490007441H/outbound - appears fixed

Rail - 0000 prefixes
These routes are imported from National Rail data. I’ve found another routesection affected (Waterloo - Westbury, Wilts) but there. I’ve raised SVC-6891 to investigate this.

Buses - 500 errors
139/490000087GF/outbound - appears fixed
e1/490007441H/outbound - appears fixed
n53/490019475P/inbound - appears fixed
r7/490005081Z/outbound - appears fixed

Buses - departureStopId does not match originator

This seems to be driven from when 2 stops on the route exist in the same StopArea (NaPTAN) or HUB area (Unified API). I’ve raised ticket SVC-6892 to look into why the latter stop is being returned as the departureStopId.

1 Like

@jamesevans Thanks for that.

To give you some more recent data, here’s the position as of the update dated 23/12/2019:

Buses - Stop removed from route
83/490000087GH/outbound
148/490003375WK/inbound
434/40004410113A/inbound

Buses - 500 errors
612/490011990N/outbound
k5/490006283E/outbound

Buses - no interval sets
hereeast-shuttle/490001338Z/outbound

no interval sets in stationIntervals and all knownJourneys have intervalId set to -1

Buses - departure stop does not match originator
This is basically the same list as in my original post

Rail - 0000 prefixes
cross-country/0000BRSTLTM1/inbound
great-western-railway/0000BSNGSTK1/outbound
scotrail/0000PSLYGST3/inbound
south-western-railway/0000BKNHRST1/outbound

I dont know where National Rail’s TIPLOC codes are converted to NAPTAN codes by the addition of a 910G prefix but, as I mentioned previously, this appears to be caused by the inclusion of the platform number in the code before lookup/conversion. As well as their inclusion in the timetable data, there are 63 of these ‘0000’ codes in the /Line/Route/Sequence data

Rail - including LO/TflRail
Although you say that the API has historically not had access to this data, /Line/Route (no parameters) nevertheless returns a list of potential starting points for all the rail services, so there is some data present to cause this, it’s only the detail calls that get the rejection message. As a simple example, the following locations are returned for c2c:
c2c/910GFENCHRS/outbound
c2c/910GLIVST/outbound
c2c/910GSHBRYNS/inbound

1 Like

Another wrinkle in the update dated 2/3/2020:

As well as all the problems detailed above, route 192/outbound has the last stop (Tottenham Hale Bus Station/490009917AP) duplicated. This does not appear in /Line/Route/Sequence
Edit:
A little bit of defensive coding later, we find:
Stop 490000054CA skipped, same as previous in 125/outbound/0
Stop 490009917AP skipped, same as previous in 192/outbound/0
Stop 40004402075A skipped, same as previous in 203/inbound/0
Stop 490015719S skipped, same as previous in 366/outbound/0
Stop 490011630S2 skipped, same as previous in 366/outbound/0
Stop 490011630S2 skipped, same as previous in 366/outbound/1
Stop 490004992E skipped, same as previous in 497/inbound/0
Stop 490000500Y skipped, same as previous in b13/inbound/0

1 Like

And further woe, updates dated 30/4/2020 and 1/5/2020:
(data taken from the latter)

I’m getting a large number of ‘Error 500 Internal Server Error’ responses, specifically, all of these:

5/490011659E/outbound
11/490012391S/inbound
12/490000173RF/outbound
14/490011285E2/outbound
15/490013766F/inbound
30/490014662W/inbound
31/490003375WK/inbound
33/490005445D/outbound
33/490009353S/inbound
36/490010204K/inbound
38/490014050D/inbound
40/490006232W1/outbound
44/490014050R/outbound
60/490001279E/inbound
72/490015061O/outbound
73/490012837K/inbound
78/490012113N/outbound
94/490004996U/inbound
100/490012020B/inbound
101/490014816E/outbound
110/490014493E/inbound
110/490015241B/outbound
117/490014493HE/outbound
122/490005869B/inbound
123/490007657W/inbound
123/490015567G2/outbound
129/490007515C/inbound
146/490006159E/inbound
156/490000247E/inbound
157/490000151C/inbound
162/490001097A/inbound
164/490013060Q/outbound
167/490007657W/outbound
168/490011760D/outbound
172/490003193S/inbound
173/490015364E/inbound
181/490001177V/outbound
184/490013852S/outbound
197/490015223C10/inbound
198/490013634L/inbound
202/490005869B/outbound
205/490003554W/outbound
228/490013297S2/inbound
240/490000087GI/outbound
246/2400A006470A/inbound
253/490000077G/inbound
253/490001127J/outbound
255/490016323E/outbound
256/490009943N/outbound
258/210021903896/outbound
268/490010471Z/inbound
274/490003327K/outbound
282/490006292R/outbound
292/210021003960/outbound
297/490014687N/outbound
298/490000009W1/outbound
299/490000053B/inbound
301/490003975L/outbound
312/490010448S/inbound
312/490012272N/outbound
315/490000012A/inbound
317/490009222A/inbound
320/490003996S/outbound
326/490004282D/inbound
331/490000197B/outbound
335/490014782S/outbound
344/490000138B/inbound
346/490015474C/outbound
349/490007258P/outbound
353/490011409S/outbound
354/490010905E/outbound
356/490012092N/inbound
357/490005167S/outbound
370/490009810M/outbound
375/490001243ZA/outbound
376/490006317B/outbound
376/490010218W/inbound
382/490020301N/inbound
389/490013559S/outbound
393/490004451O/outbound
403/40004410152A/outbound
406/490005800A3/outbound
407/40004410084C/inbound
412/490013142C8/inbound
427/490005185N/outbound
432/490007523F/outbound
436/490001016A/inbound
450/490003849W1/inbound
452/490012622S/outbound
455/490004761N/outbound
464/490010848S/inbound
468/490003871DS/inbound
468/490013100G/outbound
469/490011307H3/outbound
474/490013802W/outbound
490/4900164307/inbound
490/490018677N/outbound
491/210021703425/outbound
491/490015155E1/inbound
533/490009353S/inbound
621/490001177X/outbound
621/490016229E/inbound
696/490013465E/outbound
b13/490001205D/inbound
c1/490014050R/outbound
d8/490012904T/outbound
district/940GZZLUUPM/inbound
e5/490013714S/outbound
e10/490008519N/outbound
el3/490003150B/outbound
g1/490008080S/outbound
h9/490016764HW/outbound
h25/490000103Z/inbound
k1/490001206S/outbound
k1/490005800A12/inbound
n3/490000173RF/outbound
n7/490000173OQ/inbound
n22/490012333E/outbound
n31/490001069D/inbound
n86/490012904B/outbound
n91/490000053B/outbound
n98/490011487G/inbound
n113/490013767T/inbound
n113/490015287E/outbound
n133/490000138D/inbound
n136/490000173RF/outbound
n137/490000173JC/inbound
n155/490000151C/outbound
n279/210021703425/outbound
n551/490013767B/outbound
p13/490010208L/inbound
r1/490007559E/outbound
r4/490006756W1/inbound
r6/490001220D/outbound
r7/490005204Z/inbound
r8/490001220E/outbound
rb1/930GWAS/inbound
rb2/930GTMP/inbound
rb4/930GNEL/outbound
s3/490001020C/outbound
tram/940GZZCRWMB/inbound
u5/490005356T/inbound
w3/490000083B/inbound
w11/490005173N/outbound
woolwich-ferry/930GWWS/outbound

1 Like

It’s getting worse - there are 627 Error 500 returns after the updated dated 4/5/2020

–Edit-- still true after rollback, followed by update dated 5/5/2020

The total this time is 614 - this represents over a third of all the 1820 requests made (plus another 50+ errors along the lines documented in previous posts)

–/Edit–

Hi @nickp

We’ve been experiencing some issues with the timetable back-end recently returning 5xx codes. We believe it partly to be load-related so I’d suggest throttling the rate of your requests and hopefully that will provide a more reliable set of results.

I’ll keep you updated on the progress of a fix here.

thanks,
James

Thanks @jamesevans

I’ll give it a go with a tick delay in place and report back. I just note in passing that this is the same code that I use for /Line/Route/Sequence downloads with no such problems there.

Regards
Nick

Hi @jamesevans

Ok, I’ve tried this with both a 1-second and a 3-second tick delay, with no significant improvement. Here’s the start of my log for the 3-second run, showing the results.

Each ‘… pause n’ line is my tick delay in operation. Additionally, each ‘…retrying…’ also has a built-in 3-second delay. Just to emphasise the point, this has been working reasonably, barring all the errors mentioned above, until a couple of weeks ago.

Back to your end, James.

Regards
Nick

Log extract:

Line/1/Timetable/490004733C?direction=inbound
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/2/Timetable/490000145L?direction=outbound paused 3
Line/2/Timetable/490010444W?direction=inbound paused 3
Line/3/Timetable/490005869D?direction=inbound paused 3
Line/3/Timetable/490019475P?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/4/Timetable/490000008NW?direction=outbound paused 3
Line/4/Timetable/490000023BA?direction=inbound paused 3
Line/5/Timetable/490000039F?direction=inbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/5/Timetable/490011659E?direction=outbound paused 3
Line/6/Timetable/490003193R?direction=inbound paused 3
Line/6/Timetable/490003935Z?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/7/Timetable/490000173OQ?direction=inbound paused 3
Line/7/Timetable/490015061O?direction=outbound paused 3
Line/8/Timetable/490000235Z?direction=inbound paused 3
Line/8/Timetable/490004215M?direction=outbound paused 3
Line/9/Timetable/490003193R?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/9/Timetable/490007705G?direction=inbound paused 3
Line/11/Timetable/490007057R?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/11/Timetable/490012391S?direction=inbound paused 3
Line/12/Timetable/490000173RF?direction=outbound paused 3
Line/12/Timetable/490006652N?direction=inbound paused 3
Line/13/Timetable/490000248ZZ?direction=inbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/13/Timetable/490015443P?direction=outbound paused 3
Line/14/Timetable/490000200E?direction=inbound paused 3
Line/14/Timetable/490003794O?direction=inbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/14/Timetable/490011285E2?direction=outbound paused 3
Line/15/Timetable/490002018P?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/15/Timetable/490013766F?direction=inbound paused 3
Line/16/Timetable/490000248ZZ?direction=inbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/16/Timetable/490010015S1?direction=outbound paused 3
Line/17/Timetable/490000008R?direction=outbound paused 3
Line/17/Timetable/490000139A?direction=inbound paused 3
Line/18/Timetable/490000077E?direction=inbound paused 3
Line/18/Timetable/490003597G?direction=outbound paused 3
Line/19/Timetable/490000083G?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/19/Timetable/490003683N?direction=inbound paused 3
Line/20/Timetable/1500IM1055?direction=inbound paused 3
Line/20/Timetable/490000249B?direction=outbound paused 3
Line/21/Timetable/490009105U?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/21/Timetable/490015396S?direction=inbound paused 3
Line/22/Timetable/490000173RF?direction=inbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/22/Timetable/490011281N?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/23/Timetable/490007419C?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/23/Timetable/490007705G?direction=inbound paused 3
Line/24/Timetable/490012280A?direction=inbound paused 3
Line/24/Timetable/490015832E?direction=outbound paused 3
Line/25/Timetable/490007657V?direction=inbound paused 3
Line/25/Timetable/490008275K?direction=outbound paused 3
Line/26/Timetable/490000254QA?direction=inbound paused 3
Line/26/Timetable/490008264S?direction=outbound paused 3
Line/27/Timetable/490000097T?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/27/Timetable/490004962W?direction=inbound paused 3
Line/28/Timetable/490009631N?direction=inbound paused 3
Line/28/Timetable/490012622S?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/29/Timetable/490013767C?direction=inbound paused 3
Line/29/Timetable/490015567G2?direction=outbound paused 3
Line/30/Timetable/490011133M?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/30/Timetable/490014662W?direction=inbound paused 3
Line/31/Timetable/490003375WK?direction=inbound paused 3
Line/31/Timetable/490003698W?direction=outbound paused 3
Line/32/Timetable/490000070D?direction=outbound paused 3
Line/32/Timetable/490000127KA?direction=inbound paused 3
Line/33/Timetable/490005445D?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/33/Timetable/490009353S?direction=inbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/34/Timetable/490003634G?direction=outbound paused 3
Line/34/Timetable/490014164D?direction=inbound paused 3
Line/35/Timetable/490009843G?direction=outbound paused 3
Line/35/Timetable/490012113N?direction=inbound paused 3
Line/36/Timetable/490005345C?direction=outbound paused 3
Line/36/Timetable/490010204K?direction=inbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/37/Timetable/490010877E?direction=inbound paused 3
Line/37/Timetable/490011285E2?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/38/Timetable/490009035E?direction=outbound paused 3
Line/38/Timetable/490014050D?direction=inbound paused 3
Line/39/Timetable/490000184Z?direction=outbound paused 3
Line/39/Timetable/490009843G?direction=inbound paused 3
Line/40/Timetable/490006232W1?direction=outbound paused 3
Line/40/Timetable/490015104S?direction=inbound paused 3
Line/41/Timetable/490000008Z?direction=outbound paused 3
Line/41/Timetable/490009917C?direction=inbound paused 3
Line/42/Timetable/490006336N?direction=outbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
Line/42/Timetable/490012391S?direction=inbound paused 3
Line/43/Timetable/490000139C?direction=inbound paused 3
Line/43/Timetable/490016643W?direction=outbound paused 3
Line/44/Timetable/490001296N?direction=inbound paused 3
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error
…retrying…
Error 500 Internal Server Error

Hi @nickp

Do you know what time you performed this test?

Thanks,
James

1 Like