# Changelog of Zillow Price Tracker & Scraper - Price Drops, API & MCP (`akhil_rajesh/zillow-price-tracker`) Actor

- **URL**: https://apify.com/akhil_rajesh/zillow-price-tracker/changelog.md
- **Full Actor documentation**: https://apify.com/akhil_rajesh/zillow-price-tracker.md

## Changelog

### 2026-11-10

- The README links a new Actor: Indeed Jobs MCP Server & API.

### 2026-11-06

- The README links a new Actor: Pinterest Trends Scraper & API.

### 2026-11-04

- The README links a new Actor: Google Trends Scraper & API.

### 2026-11-03

- The Apify SDK is updated from 4.0.2 to 4.2.0 (apify-client 3.4.0 and crawlee 1.11.0 stay). Runs return the same data. A run still stops exactly at your maximum cost per run and says so: SDK 4.2.0 would let one more result through past a spent limit, and this Actor keeps the earlier behaviour, so nothing past your limit is stored or charged.
- With SDK 4.2.0, a status update that doesn't reach Apify is logged instead of stopping the run.

### 2026-11-02

#### 0.1.17 - Changes stored as an abort comes are kept

- Only changes: a run aborted while a home page was loading (the last one its Home pages budget allowed) went on to store the changes read with it after the abort had saved the history, and those homes were left out of it. The next run of the schedule reported them again, and charged them again. The run now saves the history again as it ends, so they are kept.

#### 0.1.16 - History and alerts however a run ends, stricter webhook addresses

- Only changes: a run aborted (or moved to another server by the platform) at the moment it saved a search's history could have that save overwritten by the one the abort makes. What only the run's own save held was then lost: homes delivered before a restart, the baseline of homes past Max results on a first run, and which homes had gone missing. The next run could report and charge those homes again or as new listings, and report removals a run late. The two saves now take turns, and both are kept.
- Only changes: however a run ends, the homes it stored now go into the history. A run that stopped because the dataset failed or on an unexpected error saved none of them, and one that was restarted by the platform and then aborted, stopped by an error, or met Zillow down kept only what its last attempt stored. The next run then reported, and charged, those homes again.
- Only changes: when Zillow went down while a run checked which missing homes had sold, the run delivered nothing, not even the changes it had already read. Those changes are now delivered, no home counts as missing in that run, and the sales are reported by the next run.
- Alerts: a run that is aborted, can't store its rows in the dataset, or stops on an unexpected error now posts the changes it stored. Before, those changes were never posted, since the next run already knows them. An aborted run has seconds left, so it tries each message once.
- Alerts: when a search's history doesn't answer, the run no longer posts the "alerts are set up" message as if it were a first run, and doesn't claim there were no changes.
- Alerts: a webhook URL that writes a private address in a short or numeric form (`https://127.1/`, `https://0x7f.1/`, `https://2130706433/`) is now refused, as `https://127.0.0.1/` already was. Public addresses written as numbers still work.
- Library versions are fixed: apify-client 3.4.0 and crawlee 1.11.0 next to the Apify SDK 4.0.2, so a rebuild can't bring in versions the tests haven't run on.
- The README links two new Actors: YouTube Channel Scraper and Contact Details Scraper.