Finnair repeatedly changing flight by 20 minutes

[mika_duffer]

Hi everyone,
My girlfriend and I are heading to Europe in July on rewards J flights with Finnair booked through Qantas. We have both received emails about 4 times now titled “Important - The departure date for your flight has changed” to which we always go “Ahh f—“ because we’ve already booked accom etc. The email then shows our new flight time and date and not your old one so I have to go and check my calendar to see when it was previously meant to be departing, only to find out that the departure time is different by 20 minutes!?!!! It then asks you to “confirm new departure date”.
I’m no tech guru but surely there could be some coding that if the flight date isn’t actually different then the email could be titled “Your flight time has changed” or even better - include the previous flight time in the email! This has happened about 4 times now. Unnecessary stress induction from what is just a poor notification system!
Has anyone else experienced this? Sorry for the vent but bloody annoying

 

[Quickstatus]

I would posit that airlines continually updating their passengers is a good thing. Often passengers complain they were never told. That QF successfully contacted you means that the communication channel is validated. I would actually worry if I don't hear anything.

While 20 min might not seem like much, QF does not know the true travel intentions of their passengers. They might for example have connecting flights and the 20 minutes might make an onward connection problematic.

I understand your point that it may seem excessive.

 

[mika_duffer]

I would posit that airlines continually updating their passengers is a good thing. Often passengers complain they were never told. That QF successfully contacted you means that the communication channel is validated. I would actually worry if I don't hear anything.

While 20 min might not seem like much, QF does not know the true travel intentions of their passengers. They might for example have connecting flights and the 20 minutes might make an onward connection problematic.

I understand your point that it may seem excessive.

Oh absolutely. I’m complaining about the way in which it’s communicated. The subject says the date has changed - the date has not changed.

 

[Quickstatus]

. maybe too complicated for their IT systems

 

[LostRedditor]

> from datetime import datetime
> originalDepartureTime = datetime.fromisoformat('2024-07-13 07:20:00')
> newDepartureTime = datetime.fromisoformat('2024-07-13 07:40:00')
> newDepartureTime == originalDepartureTime
False
>

see, the Date objects are different. Welcome to software engineer thinking

however, on a more serious note, no one has probably ever raised this with them. And if someone actually does, they'll do a quick cost/benefit calculation and either create a work ticket in their backlog or they'll toss it in the "not worth it" basket. And if their backlog is as big as the ones in my team, it'll be a while before they get to it