DOM upgrade request puzzle

[JohnM]

I've recently booked PER-SYD-PER in whY (Q bucket) on flights that EF shows having at least one U seat (and the QF booking engine confirms as having a Business reward seat available).

However, when I put in a request for an upgrade, it was not immediately granted. It remains on request. Previous experience has been that DOM upgrades are usually approved immediately under circumstances where U availability id showing. I have assumed that if U is available, it will go to an upgrade request.

Has something changed, did I just get repeatedly lucky previously for other reasons, or am I missing something?

(BTW, there is a reason why I bought the whY seats and then sought an upgrade, rather than just taking the J seats as a reward straight-up.)

 

[mannej]

Hey John it's a known bug. A call to QF will sort this out manually. Others have tried to cancel the request and resubmitted with success, but it doesn't always work.

 

[Mattg]

If there is 1 U seat and you're trying to do 1 upgrade to J, I don't see any reason why it shouldn't come through straight away. Cancelling and re-submitting the upgrade request should hopefully fix this.

 

[JohnM]

If there is 1 U seat and you're trying to do 1 upgrade to J, I don't see any reason why it shouldn't come through straight away. Cancelling and re-submitting the upgrade request should hopefully fix this.

Tried that, mate! I'll call.

 

[JohnM]

All sorted. Booking started life as a Sabre PNR, with an Altea PNR that enabled me to (supposedly) MMB in QF. Problem was that the e-ticket number didn't transfer across, leaving some link behind the scenes broken.

 

[Mattg]

All sorted. Booking started life as a Sabre PNR, with an Altea PNR that enabled me to (supposedly) MMB in QF. Problem was that the e-ticket number didn't transfer across, leaving some link behind the scenes broken.

Wow... glad you got it sorted, and good to know that this isn't a change in policy!

 

[JohnM]

Wow... glad you got it sorted, and good to know that this isn't a change in policy!

Exactly... :shock:.