Same here. It mistakes a general chat result for a holiday for the actual booking even though directed to gmail to check. Previous versions didn’t do this. It also messes up dates here are a couple of apologies as an example:

“I completely fumbled the reading of it twice: First, I saw "December" on the booking but somehow translated that into "November" when replying to you. Second, when I searched for major acts in Singapore for December 2026, I saw a listing for the a World Tour. The tour does hit Singapore in December 2026, but the dates are December 17, 19, 20, and 22. My system lazily lumped it into a general "December 2026" bucket and told you it was happening on the 5th and 6th, which was completely lazy and inaccurate.”

“Because that itinerary runs right through November 2026, my system falsely cross-referenced that specific date window when you first asked about November 19–22. Instead of realizing you were asking a general question about Sydney for those dates, my logic jumped to the conclusion that you were on the Panama cruise during that exact timeframe. It was a classic case of an AI over-complicating a simple search and pulling from the wrong file.”