Gold Member
Established Member
- Joined
- Feb 12, 2008
- Posts
- 2,166
I’m very comfortable and familiar with making an AA booking using points for QF domestic flights. That includes the El Segundo method and other little tricks. But in the past few weeks I’ve noticed that no matter which flight I select (MEL-PER-MEL for example) for several months out, it throws up an Error just after the Passenger info and the subsequent seat selection page. Specifically, the error page states:
I have tried selecting different flights, multi-city, desktop/IOS App, logging in from US/AU regions, different accounts, different browsers etc, but I get the same error message each time.
I think I found a workaround which I’ve tested on different flights and it allows me to progress to the next page (payment options). The key is to select the small text hyperlink “Continue without seat Selection” located just below the obvious blue button labelled “Continue”. So it seems that the seat selection page input is the cause of the error.
Anyone else have experience with this problem?
This page must have taken flight
There are a few FT threads talking about the same problem going back over 4 years for all sorts of flight, not just partner QF flights. It appears to be a known temperamental bug within the AA.com booking engine for both paid and award flights. There doesn’t appear to be a fix other than to call and have an agent ticket it for you waiving call centre fees due to online issues. BUT, for us Aussies that means we need to call Fiji who will tack on an Australia redemption fee for each booking since the El Segundo method is not viable.I have tried selecting different flights, multi-city, desktop/IOS App, logging in from US/AU regions, different accounts, different browsers etc, but I get the same error message each time.
I think I found a workaround which I’ve tested on different flights and it allows me to progress to the next page (payment options). The key is to select the small text hyperlink “Continue without seat Selection” located just below the obvious blue button labelled “Continue”. So it seems that the seat selection page input is the cause of the error.
Anyone else have experience with this problem?
Last edited: