Magical train "cancellation" today

[whole diary]

[gpn01]

This morning's 07:08 Maidenhead - Paddington showed on the platform information screen as delayed by around 20 minutes so I managed to squeeze onto the 07:03.  A text message then came through to say that the 07:08 was now cancelled due to signalling problems.  Conjured up images of a trainload of passengers sitting on the train just outside Worcester (or wherever it starts) being told that the train they're on has been cancelled!  A few minutes later another text came through to say that the train was operating again. I can only presume that someone, somewhere, inadvertantly set the status of the train to cancelled, realised their mistake, and reset it.

Did make me wonder....when a train shows as "delayed" and then "cancelled" is it more likely that it was not going to operate in the first place and is the fiddling with status's to do with achieving some performance monitoring goal?

[super tm]

This train did run but it did not stop at maidenhead due to late running.  So from a passenger at Maidenhead's point of view it was cancelled.

[phile]

This sort of information can sometimes be misleading.   Agreed that the train was cancelled so far as Maidenhead was concerned.      On occasions trains to and returning from Cardiff terminate short and I recall one occasion when a Cardiff to Portsmouth I was intending to travel  was dispayed on the CIS^▸ (Customer Information System) and announced as Cancelled.   However, I thought I would travel to Newport and wait there instead, but on arrival there found the train waiting, turning round there due to incoming late running.    The automated systems fall down in such circumstances and fail to display real time information.   Fortunattely when this does occor, a live voice informs intending passengers and the XX25 FGW^▸ (First Great Western) departure to Paddington is held until the Portsmouth departure time of XX30 to convey them to Newport.    If one has to rely on the Automated systems only, passengers can be let down because the facility is not there to inform people that their train is starting frm Newport.

[gpn01]

This train did run but it did not stop at maidenhead due to late running.  So from a passenger at Maidenhead's point of view it was cancelled.

Just as well that I ignored the message to say it was reinstated then. Mind you I was on the 07.03 when the text arrived.
Now at Paddington trying to find a train home as they're all cancelled or delayed.  No mention why. Grrr.

[ChrisB]

Signals at Southall....

[phile]

This train did run but it did not stop at maidenhead due to late running.  So from a passenger at Maidenhead's point of view it was cancelled.

Just as well that I ignored the message to say it was reinstated then. Mind you I was on the 07.03 when the text arrived.
Now at Paddington trying to find a train home as they're all cancelled or delayed.  No mention why. Grrr.

Lack of information again.   I thought special attention was to be given to this following severe problems last Winter

[Ollie]

Was a very clear and detailed announcement at Paddington when I walked up from the Underground.

[johoare]

When I got there (7.25ish) the indicator boards said that the signal trouble was currently  causing 10 minute delays.. Ha ha ha ha ha excuse me while I stop laughing and I won't believe it next time... Ps there were no announcements while I was there and I was there for about 20 minutes (on trains for a lot longer)..

[gpn01]

Was a very clear and detailed announcement at Paddington when I walked up from the Underground.

I was there from 21.30 and nothing was said. Made worse when sitting on 21.48, hoping to at least get to Slough. At about time due for departure it was announced on train that it would now be delayed and that Slough passengers should go to train on platform 1 instead.
Typing this at Maidenhead as a train passes through Maidenhead at 07.10. Presume it's the canceled 07.08 that I didn't get an alert about this morning!