Aircraft? Fare class?

2 flights this Saturday. Both F9 R9.

First one upgraded at the 96 or thereabouts.

Second one did not upgrade, still F9 R9, 4 hours after the 96.

EUA bugs still live on...

*CPU, not EUA.

Why is that a bug?

EWR - LAS on Friday night there were at least 18CPUs (mine cleared t-96) and one empty F seat. I strangely enough the upgrade standby list was empty - I've never seen this before but guess this is NOT an elite heavy route? This was the 753 so a decent amount of F seats as well

Well when the new CPU system was introduced with SHARES rather than running when inventory opened up we were all told that it would only run once a day at the upgrade windows for that flight.

That was sort of what everyone expect given the representations that were made. :rolleyes:

But you are correct, its clearly not a bug, its part of a deliberate strategy to hold back and try to sell as many seats as [and I know you hate the term, but hey, not my problem] TODs. :eek:

All part of UAfkaCOdbaAllergent's great plans for all of us. :D

Looks like you never actually read the post. This has nothing to do with upgrades happening outside a particular window.

And there's the fact that I never said it wasn't a bug - I asked a simple question.

Agree that it's an (unsurprising) bug

While R space doesn't guarantee CPU running, there is of course high correlation...and still being R9 after the 1K window and an UG not going through is highly suspect.

So, R9 at 96 hours means all 1K's should clear?

And if they don't, it is 'highly suspect' or perhaps 'its part of a deliberate strategy to hold back and try to sell as many seats as TODs.'

Are there any other plausible explanations? Or only the ones that you believe are part of UA's insidious plan to chase away elites?

It's been documented many times that a single out-of-sync res will hold up the entire process. And it's also been stated by our former UAI that CPU should be running if R>2. This seems like a textbook example.

UA chasing away Elites has been only partly planned - a lot of it has been incompetence too. A wonky auto-upgrade process is but one example.

Is this still happening? I do recall higher frequencies of this shortly after the system merge...

This I don't recall reading at all... Are you certain?

CPU is the type of upgrade.

EUA is the system that processes the upgrades.

EUA is what's broken.

At 96 hours, the EUA should have swept the flight and allocated something. The fact that the flight has remained F9 R9 well beyond that is suspect.

As I do with all such EUA anomalies, I call in and request a manual upgrade or a bug report be written. I usually end up with the latter.

EUA doesn't exist anymore - it was an old CO process. This is United now.

You're making the rookie mistake that you chastise people for here on a regular basis. This simply isn't how the system works - it's very possible that the CPU process *did* sweep the flight and allocated *nothing*. That isn't a bug if it happens. You or I don't have the data to show whether that happened or not, so I'd be fascinated to know how you know this a bug.

The existence of R inventory has no bearing on whether the CPU process will run. How many hundreds of examples and statements from UA representatives are needed to show that this is the case?

And as for calling in? What makes it *your* upgrade to get manually? If there are 10 people ahead of you on the list and the CPU process doesn't hand out any upgrades for whatever reason (e.g., high likelihood of buy-ups on this route / flight / day of week / month / year, data shows likely last-minute purchases on this route / flight / day of week / month / year, didn't run due to an error, or any other reason) why does that automatically mean it's your upgrade to get? And what do you tell them to include in these "bug reports"? I'm pretty sure I know what they do with them ;)

This is a classic case of somebody with no insight into the actual data putting what they think is two and two together and arriving at a completely erroneous conclusion. You just don't have the data to be able to determine what you think you can determine.

Nonsense. EUA exists. The system is still called EUA. If you read a PNR, you'll even see if EUA upgraded the passenger.


The last I heard from a UA rep was that EUA will dump all of R except in some markets, 1-2 R seats. A holdback of 9+ seats is not the design.


I don't know if it's my upgrade or not. All I know is it didn't run like it was supposed to. That's a bug, and that's what I report.


The facts are R did not go down and I did not clear. Since R > 2, that's a bug. Nothing erroneous about it, something's wrong with the flight.

Well, what do you know... Right after I posted this thread, I got my first upgrade since January, BOS-EWR on a A319. No hopes for IAD-SFO tomorrow, unfortunately.

I side with those who think something is still not right with the CPU process. Flying ORD-SFO last week with jchiguy1partner; same PNR, status (1K), fare class (tix bought together) and we both have exactly the same PQM this year. I went to check us in at T-24 and somehow I got upgraded while he remained on the wait list (which split the PNR). Got to ORD, headed to the gate and he appeared at number two on the upgrade screen. He went up to the agent at T-45 min to inquire about his chances and lo and behold she handed him a new FC boarding pass. I'm still not sure exactly how all that happened.