Release notes

On the morning of 29 October, UK clocks changed for Daylight Savings Time. Due to a bug, all journeys on 29 October were showing as late, even if they were on time or early.

This meant that instead of the Journeys List looking like this:

It looked a bit more like this:

The band of orange on 29 October shows that all the journeys for that day were late at the first stop – which wasn’t the case. It’s apparent that this number of delayed trips is abnormal compared to typical on-time performance across the rest of the month.

We’re really proud of how the Journeys List makes it easy to see where things aren’t quite right, and in this case it quickly became apparent that our daylight savings calculations had gone awry.

We’ve replayed everyone’s data for 29 October to correct matching issues, and made changes to make sure this doesn’t happen again.

To double-check your on-time performance looks correct for 29 October, head to Mosaiq Insights and choose a busy service from the KPI Dashboard or the Services List. Then look for this button to see the Journeys List:

Drill down into any of the trips for 29 October and you will see detailed journey-level information that will clarify if any remaining lateness is justified.

If you have any other questions or things still don’t quite look right, please do not hesitate to get in touch with your account manager.