We have been performing a migration during which we updated a large number of reservations in a short time. Some of our integration partners are batching reservation updates by fetching updates from a fixed update date interval. Since there is a limit to the number of updates they can process in one batch, their reservation update processing was blocked.
Additionally, some properties using the Reservation report with the filter on update date were unable to use the report because the number of returned reservations exceeded the report limit.
We have reprocessed all the migrated reservations and changed (only) their update date so that the updates are more distributed over time.