Why does TR feed has searches with identical correlation ID, but varying uuids?

It happens because of combined search results. If the first search / session is displaying on mobile the combined search result, the 2nd session is from the expanded number of itineraries shown to a traveller. Both share the same correlation ID (request ID), but the Travel Rankings PUSH UUIDs are different because 2 distinct API calls are made to a partner Meta API.