# Changelog of Booking Reviews Scraper (`lergassy/booking-reviews-scraper`) Actor

- **URL**: https://apify.com/lergassy/booking-reviews-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/lergassy/booking-reviews-scraper.md

## Changelog

### 2026-10-18

- Every run now ends with a one-line status: how many reviews came back and how many inputs failed (free). Before, a run that did not hit your cost limit finished with no status at all.
- A hotel that Booking.com does not sell right now (it answers its own search with "Internal Server Error", seen on the Ritz Paris) now gets a plain explanation in its error row instead of the raw GraphQL error. Nothing is charged for it.

### 2026-10-12

- Under "Max cost per run", calendar, property and review rows are held back and charged by their own price, so a capped run never charges for a row it did not deliver; the status line always says the run was capped.

### 2026-10-02

- Memory is now sized to your input: small runs use less, large runs get more.

### 2026-10-01

- Fixed runs with a maximum cost stopping before they reached your limit.

### 2026-09-30

- New "Only new rows" option (`onlyNewRowsStore`): name a memory, schedule the Actor, and later runs write and charge only reviews you have not received before.

### 2026-09-29

- Hotel URLs are now a required input, so an empty form is caught before the run starts.

### 2026-09-27

- Runs stop cleanly at your maximum cost instead of being aborted; nothing beyond your limit is written or charged.

### 2026-09-22

- Initial release: Booking.com guest reviews for any property, one row per review, with score, title, liked and disliked text, stay date, country, traveler type, room, nights, hotel reply and photos.