Tier Tracker updates taking forever?
#1
Original Poster
Join Date: Jun 2013
Location: FSD
Programs: AA CK, DL SM, UA PS, HH Diamond, Bonvoy Titanium , Hyatt Globalist, Global Entry, CLEAR
Posts: 458
Tier Tracker updates taking forever?
Is it just me or is the tier tracker update taking longer than usual for the first of the year reset?
#4
Join Date: Jun 2017
Location: Tbilisi, Georgia
Programs: HH Diamond, A3 Gold (*G)
Posts: 48
#6
Suspended
Join Date: Aug 2010
Location: Vancouver
Programs: CX DM, SQ TPP, QF GO LIFE, OZ*G LIFE, Marriott TIT LIFE, WOH GLOBALIST LIFE, HH DM, BA GO LIFE
Posts: 598
It's already 16 January and Hilton is telling us to hand tight whilst their incompetent IT team takes their sweet time to do the reset whilst all other hotel programmes have undertaken this within the same day on the 1st January 2019.
This is rather unacceptable from Hilton's end and with zero communication, its adds to the overall frustration.
This is rather unacceptable from Hilton's end and with zero communication, its adds to the overall frustration.
#7
Join Date: Feb 2013
Location: DCA
Posts: 7,769
Can anyone with an IT/CS background hypothesize as to what might possibly be so difficult about this kind of thing so that maybe I can have some sympathy? To a layperson like myself who has taken a couple CS classes this seems like something that would be built in with a couple lines of code, but clearly I must be wrong...
#8
Join Date: Feb 2017
Location: JNB
Programs: HH Diamond, Marriott Silver
Posts: 24
I suspect some bad design, must be a lot of outsourcing / contract workers for the development and the basic understanding of the loyalty system not there. Just coders coding away without fully understating what exactly they are to coding.
Also cannot fully blame coders, there are too many persons involved and looks like communication breakdown between all of them.
I think also trying to make all the systems work, from old legacy to new web/mobile and a lot of hotels using different modules etc.
Too many things just went wrong here.
Also cannot fully blame coders, there are too many persons involved and looks like communication breakdown between all of them.
I think also trying to make all the systems work, from old legacy to new web/mobile and a lot of hotels using different modules etc.
Too many things just went wrong here.
#9
Join Date: Mar 2014
Location: San Francisco
Posts: 1,351
It's already 16 January and Hilton is telling us to hand tight whilst their incompetent IT team takes their sweet time to do the reset whilst all other hotel programmes have undertaken this within the same day on the 1st January 2019.
This is rather unacceptable from Hilton's end and with zero communication, its adds to the overall frustration.
This is rather unacceptable from Hilton's end and with zero communication, its adds to the overall frustration.
#11
Join Date: Jan 2010
Location: DCA
Programs: AA EP, HH LT Diamond
Posts: 1,001
#12
Join Date: Jun 2016
Posts: 9
It's actually not too early to start worrying about it, it would be nice to know where I stand. I had quite a few roll-over nights, plus 12 days in January already. I'm starting to plan February travel and would be nice to know when I should switch over to Marriott to get my 75 nights there as well.
As per the IT questions... Isn't this the first year of roll-over nights? My guess is something went very wrong in how they calculate and apply those.
As per the IT questions... Isn't this the first year of roll-over nights? My guess is something went very wrong in how they calculate and apply those.
#13
Join Date: Jun 2013
Location: norwich, uk
Programs: hhonors diamond
Posts: 5,397
Can anyone with an IT/CS background hypothesize as to what might possibly be so difficult about this kind of thing so that maybe I can have some sympathy? To a layperson like myself who has taken a couple CS classes this seems like something that would be built in with a couple lines of code, but clearly I must be wrong...
#14
Join Date: Feb 2013
Location: DCA
Posts: 7,769
Yes, it would seem to me that each customer would be a record in the database, an entry would be made for each stay (including the dates), and then something akin to a single call of a "COUNTIF" type function could be used to determine how many stays fall in the given period (in this case, 2019). But obviously it is not that simple, I guess...