Hyatt Website
#1
Original Poster
Join Date: Feb 2009
Posts: 6,605
Hyatt Website
Is anyone else having trouble looking up reservations and see account activity, etc ?
I have been trying since last week and still see this message.
I have been trying since last week and still see this message.
Sorry, your past activity is unavailable at the moment.
Please try again shortly. If the issue persists, please contact us
#2
Join Date: Jul 2009
Location: IAH
Programs: UA 2MM, Hyatt Diamond, SPG Gold
Posts: 2,162
Is anyone else having trouble looking up reservations and see account activity, etc ?
I have been trying since last week and still see this message.Sorry, your past activity is unavailable at the moment.
Please try again shortly. If the issue persists, please contact us
I have been trying since last week and still see this message.Sorry, your past activity is unavailable at the moment.
Please try again shortly. If the issue persists, please contact us
This probably should be moved to Goldpassport.com (as well as new WorldOfHyatt) New Issues and Website Problems Thread
Last edited by skj; Aug 6, 2019 at 4:40 pm Reason: Add existing thread
#3
Original Poster
Join Date: Feb 2009
Posts: 6,605
I see that most frequently in Edge and less frequently in Firefox and Chrome. I'm not sure why it makes a difference, but you might want to try a different browser.
This probably should be moved to Goldpassport.com (as well as new WorldOfHyatt) New Issues and Website Problems Thread
This probably should be moved to Goldpassport.com (as well as new WorldOfHyatt) New Issues and Website Problems Thread
Thanks, I was seeing that message using Chrome, IE did the trick
#6
Join Date: Jul 2012
Location: Madison, WI
Programs: Hyatt Globalist
Posts: 973
This. I frequently get these weird errors where pages won't load or it won't show my history properly. My suggestion that works well for me is to have Chrome automatically clear ALL cookies from hyatt EVERY TIME I close my browser. That did the trick and now I rarely have issues (and when I do, just closing and re-opening my browser fixes it)