The definitive thread on Qantas IT gripes

[henrus]

Just use a multi-city search and it works fine (even if just searching a single leg or a return).

 

[RB001]

Using the multi-city tool, I was able to get through to payment page for J and Y SYD-CTS RT (J around $6K, Y under $2K - in line with HND prices). Pretty sure the seat maps had tumbleweed.
Could also see plenty of YVR for $11-12K RT.
I haven't finalised my year-end plans, so had no reason to push the button.

 

[lsmi4126]

Using the multi-city tool, I was able to get through to payment page for J and Y SYD-CTS RT (J around $6K, Y under $2K - in line with HND prices). Pretty sure the seat maps had tumbleweed.
Could also see plenty of YVR for $11-12K RT.
I haven't finalised my year-end plans, so had no reason to push the button.

Yup - still getting $22K. I think the personalised pricing algorithm has me. Skyscanner and Google still showing $12K.

 

[RooFlyer]

Well, you beauty. Two hours after I noticed it, it now finds DPS and other ports ex MEL, HBA, BNE etc but finds nothing ex SYD.

They still want double the VA price for same B737 MEL-DPS and of course no award seats. Yet plenty will pay this! Bonkers.

Plenty of J award availability on SQ.

 

[SYD]

Not so much a gripe but curious observation. I have two seperate CR bookings SYD-HKG//HKG-SYD. The outbound seat map shows PAX initials as usual (FMS names) but the return shows SFM. It’s ticketed as usual First Middle Surname.

Is that a curious Chinese language thing or convention?

 

[RealtimeY]

It looks like a localisation that happens when you get directed to an international QF page on that screen that appears whenever you make a search for trips originating outside of Australia. Certainly it's both convention and language.

Here's the booking info page that appears when you book SYD-HKG vs HKG-SYD. Slight but logical differences - and also I suspect how some people end up entering their name in the wrong order on tickets.

AU


HK

 

[drron]

Well they took the intern who looks after the Wellness app to try and fix your booking problems. For the second day the wellness app is recording about half the steps my iPhone is recording. A little message comes up about they knowing of the problem and are trying to fix it shortly.
Just a smat way of reducing the points they give away is my conspiracy theory.

 

[henrus]

Just a smat way of reducing the points they give away is my conspiracy theory.

Time to send in a complaint and ask for more points?

 

[Boeyn]

Stumbled across an interesting glitch with the QFF points total in the iOS app/desktop website today.

I've haven't ever noticed any calculation errors/lag between transactions posting and the total updating. However, today, 4 x Citi Qantas Rewards transactions posted to my account early this morning (#pts, ###pts, ###pts, and 10,000 pts), but as of right now, my points total has only updated to reflect the first three (and instead of being 51###, it was showing as 41### instead):



I was waiting on these transactions to post before I cancelled this CC, so was curious about whether it was a calculation/lag error, or something about the 10k transaction that meant it hadn't finally "posted".

When the variance was still there 18 hours after the transactions had posted, I got curious enough to look at the API calls/responses that are made when the transaction history page is loaded, to see if I could find an answer.

In short, I couldn't see anything funny about the missing transaction in the API responses. But I did find a bunch of API calls where the points total was (and wasn't) correct (see screenshots below).

I'm not a professional developer by any means, but it seems pretty odd to me that QFF's production environment would have a handful of API endpoints that inconsistently calculate the total points balance, rather than using a uniform function to do so (eg. what if the endpoint that is used to check if I have enough points for a redemption overstates my total?).

Is there is something odd about the 10k transaction? Or are QF's developers just scrappy? We'll probably never know

The wrong totals:

https://api.services.qantasloyalty.com/member/#######/account



https://accounts.qantas.com/auth/member



https://api.services.qantasloyalty.com/member/#######/frequentflyer/topuppoints



The right totals:

https://api.services.qantasloyalty....e=2024-10-23&toDate=2025-01-23&start=0&size=0



https://api.services.qantasloyalty.com/member/#######/points-summary

 

[RooFlyer]

Or are QF's developers just [s]coughpy? We'll probably never know

If you don't mind the amendment above, then I think we do.

 

[drron]

The wellbeing app Is still not counting. Hit the customer contact and it comes up Error 502 Bad Gateway. Unfortunately for them i had their email address from a previous problem. Now they just have to answer.

 

[sudoer]

Now they just have to answer.

Tell them you are refusing to use your legs until you hear back - that should hurry them up