Originally Posted by
alex_b
As an IT person I don't find this incredible at all. UA is using a large complex legacy IT system with multiple subsystems responsible for different parts of the operation. It is almost certainly a non-trivial task to have open R space kick-off the upgrade list processing, it will also need to be weighed in amongst other code fixes that need to be done some of which might affect a larger customer segment, be required to meet legislation or be costing UA money.
There are always bugs in code, the fact they haven't been fixed yet says very little about the ability or desire to fix them in future.
+1! Not trying to quibble, but I'd argue this is not a bug, that requires a "fix" when they have time, but probably rather a rather major architecture decision in SHARES made long ago, namely that WL processing cannot start at any arbitrary time, triggered by something external like bucket availability. Of course, much easier to program that way. For all we know, in the current system someone has to carry a deck of punched cards from one room to another in IAH to start the WL processing. Anyway, revising the architecture of the system can be, as you point out, an enormous job. They may never do it, until they move away from SHARES in the year 2030.