MIG wrote

It just looks like the system was charging completely the wrong fares
to everyone and they couldn't miss it.

So I don't infer that the inexcusable situation where people are
repeatedly getting overcharged, because the system strings separate
resolved journeys into one and then decides that the resulting
journey
is too long and splits it into unresolved/unstarted journeys, is
likely to be addressed in such a helpful way.

But we have already had a automatic refund reported on this NG (2 days
after the poster had called the helpline IIRC).

Thus post-processing may be a regular item, especially when the current
gate logic cannot detect an overcharge.

--
Mike D