Current stay missing from app
 

I’m checked in and been here for a few days. The stay has disappeared from the app but shows in website.

Any workarounds/fixes?

I had this happen last week and was unable to get the stay to show up again in the app. The stay did post correctly the day after I checked out.

Also happening to me currently. Must be a bug/glitch.

Happened again mid stay.

Happened to me a few days ago in the middle of a 5-night stay. Subsequently the stay properly credited (particularly quickly, in fact). I’m noticing other visual issues in the app as well, so they probably pushed out a bad update that broke some stuff.

Happened to me (on .App and .Com) late April after 13 nights with 5 remaining.
Hotel front-desk said there was an update to Opera system over the weekend. Ok, but reservation did not re-appear. Made sure Folio received by email PDF before leaving the property.
Emailed to Consumer Affairs before checkout. No reply.
Stay posted normally

Another issue: made bookings at two properties 15 minutes apart ...one property: no email confirmation and did not appear on .Com or .App until 24-36h later.
When email confirm did not arrive in 10 minutes, screenshot the webpage of booking with confirm# and emailed Consumer Affairs.

I think Hyatt is moving from a self hosted instance of Opera (albeit on cloud infrastructure) to the next generation Opera hosted by Oracle.

(Local) Self-hosted could be the reason for problems with existing and new reservations at specific properties.

After some system program code update, wouldn't it make sense to repopulate the reservations (database vs program code) ?

Rather new to Hyatt, but in general when something (eg. reservation) disappears or doesn't appear to begin with, initial thought is the "system" doesn't know and so the property might not have your new reservation and existing reservation might not receive credit for nights/points.

If you look back at some of the threads here, there were 2 issues in April that seem to be what you’re describing.

Reservations were having issues loading and even if they did, it was incredibly slow. Confirmation emails were delayed by a day or so.

Both were temporary glitches that have been fixed.

I think the general practice these days is you plan the migration for $X date. All reservations on or after $X are populated in the new system.

On $X, you flip all the interfaces across to the new PMS. You let the existing in house reservations run in the former system and as they check out you gradually burn down the pile until everybody is being handled in the new system. Average length of stay at a typical hotel is 1.9 nights.

Yes that requires some extra work to manually post financial transactions in the old system - and you run into some quirkiness with things like the App - but you eliminate the data migration risk. You also can easily rollback should you run into issues.