"stop removed from route" error for Timetable requests

[acuth]

Timetable requests for some tube services

• Line/xxxx/Timetable/stop-id?direction=yyyy

continue to return

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.

where the stop-id was obtained from the corresponding sequence request

• Line/xxxx/Route/Sequence/yyyy

For example inbound Victoria and Jubilee lines at Green Park - 940GZZLUGPK. Oddly both of those examples work fine for outbound services and the Piccadilly line works in both directions.

This has been ongoing for some time and I was wondering whether I should be waiting for a data fix or if there is some workaround?

[LeonByford]

Hello, welcome to the forum!

Would you mind sharing some example URLs? The following are working for me:

• https://api.tfl.gov.uk/Line/victoria/Timetable/940GZZLUGPK?direction=inbound
• https://api.tfl.gov.uk/Line/jubilee/Timetable/940GZZLUGPK?direction=inbound

[acuth]

Hi Leon,

Thanks for looking at that.

Both requests return quite a lot of data but in the inbound request the timetable element is empty and accompanied by a statusErrorMessage

[LeonByford]

Thanks for clarifying. I am able to reproduce the issue, and we’re now investigating this.

[acuth]

Just an update to say that a quick test of (non-overground) stop-line-direction combos would seem to show 128 examples of this issue

[richardhawthorn]

I’ve been seeing the same issue.

When attempting to get the timetable information for Tube, Elizabeth and DLR I get the following results

Returns schedules : 688 results
No Schedule: 254 results

The same gaps in schedule data can be observed on the official timetable pages, for example the below page shows no timetable information.

Northern line timetable

[LeonByford]

Hi, an issue in one of our systems was identified and we are preparing a fix.
Sorry about this in the meantime.