This problem, which was a major bugbear in 2019, has not gone away. Lst week;s update saw examples for ther 18, 32 and 85.
I will concentrate on the 32 because it is so obviously wrong.
A set of WTTs under Service Change Number 54180 and dated 8th February were in place for some months. These were temporary timetables with reduced frequencies during works in Cricklewood.
A further set under Service Change Number 54425 and dated 9th May were uploaded around 12th May. These were for the reversion to normal timetables once the reduced frequency was no longer considered necessary.
So far so good but in this week’s update it was back to SCN 54180.
Looking at the Datastore file of Journey Planner timetables, it appears that a third set of WTTs (SCN 55176) has kicked in.
So, one the face of it the system has recognised that 54425 is no longer current but has somehow managed to revert to the even less current 54180, which must have been marked as expired when replaced by 54425. It may well be that files for 55176 were unavailable but reverting to a set that is two versions out of date would be an odd response to this.
I appreciate that in practice special timetables have been (and may well still be being) operated but that should not disrupt the process, nor has it for nearly all other routes.
Is it possible for someone to look a this example and track down exactly what has happened?