# Changelog of Scraper for TripAdvisor — Restaurants, Hotels & Reviews (`logiover/tripadvisor-scraper`) Actor

- **URL**: https://apify.com/logiover/tripadvisor-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/logiover/tripadvisor-scraper.md

## Changelog

### 2026-10-15

- Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
- A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
- A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.

### 2026-10-12

- Restaurants, attractions, location search, details and free-text locations work again: TripAdvisor's pages sit behind DataDome, which refuses datacenter and residential exits, so these requests now go through Apify's UNBLOCKER route.
- Hotels mode goes deeper: after the fast hotel shelves (~25 hotels) it continues through the hotel list pages to the requested number.
- Network errors ("socket disconnected before secure TLS connection") are retried instead of failing the run; the time budget follows the run's real timeout.
- Every Actor process now caps the JavaScript heap at ~70 % of the run's memory. The platform default lets the heap grow until the container is killed (exit 137), which showed up as random failed runs.

### 2026-09-23

- Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
- Run reliability reviewed: 96.7% of public runs succeeded in the last 30 days.
- Input schema, output schema and pricing configuration reviewed.

### 2026-09-01

- Fleet-wide health check. Verified against this Actor's real run history: 30-day success rate, output row counts, per-field fill rates, and peak memory against the configured memory limit.
- Reviewed for the failure patterns that have cost this fleet runs — unguarded proxy setup, retry loops that can outlast the run's own time budget, and full-page HTML parsing that can exhaust a small container.
- No change to input, output fields or scraping logic.

### 2026-08-11

- Maintenance release: refreshed the build and dependencies.
- Re-verified live execution, non-empty structured output and dataset field/type integrity.
- Reviewed reliability (retries, pagination) and output quality as part of a full-fleet QA pass.

### 2026-08-01

- Recovered the hotel and review variations through Tripadvisor's current public registered GraphQL operations.
- Defaulted empty/Console input to the Rome hotel shelf (`g187791`) so it does not depend on challenged autocomplete.
- Limited blocked responses to one residential-session rotation and retained explicit fail-closed behavior.
- Added current surface status, persisted-query recovery guidance, typed output fields, and curated validation inputs.
- Legacy HTML/TypeAhead modes remain available for compatibility but are documented as upstream blocked on tested Apify residential exits.
- Completed the August 2026 full health check: verified empty/programmatic default, Console UI default, and two source-informed alternative inputs on Apify.
- Confirmed successful live execution, non-empty structured output, dataset-field/type integrity, and logical sample quality within the 5-minute quality window.
- Kept the last successful residential proxy session, browser fingerprint and cookie jar sticky across typeahead and subsequent list/detail requests; blocked sessions now rotate together with their cookies.
- Added blocked/challenge and response-structure guards so an entirely blocked or structurally unreadable run fails explicitly instead of reporting SUCCEEDED with an empty dataset.
- Corrected priceLevel normalization so ranges such as $$ - $$$ produce the valid lower band 2 instead of the impossible summed value 5, while preserving the raw priceRange.
- Aligned explicit URL priority, the UI maxResults prefill, locale headers, input copy and README claims with best-effort source coverage.
- Recovered hotels and reviews through Tripadvisor's current public registered GraphQL hotel-shelf and review-list operations, repeatedly verified over Apify RESIDENTIAL routing without a user key or cookie.
- Moved empty input and Console defaults to hotels plus Rome geoId g187791 so the healthy path does not depend on the currently challenged TypeAheadJson surface.
- Limited blocked responses to one residential-session rotation, kept explicit fail-closed behavior, and documented the persisted-query rotation recovery path and current BLOCKED status of legacy HTML modes.
- Added typed GraphQL dataset fields and curated explicit-URL variations for Rome hotels and Michelangelo reviews.