# Changelog of Pazar3.mk Scraper - North Macedonia Listings (`logiover/pazar3-macedonia-marketplace-scraper`) Actor

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

## Changelog

### 2026-10-12

- Fixed: every run on the default proxy failed with `BLOCKED`. Pazar3.mk now only answers visitors from North Macedonia and neighbouring countries, and Apify's datacenter IPs were refused on every page. Requests now go through Macedonian residential IPs, with Balkan residential IPs, Apify's unblocker and the datacenter pool as fallbacks.
- Fixed: the site's first-visit "loading" page (HTTP 503) is no longer hit repeatedly — its visitor cookie is reused for the rest of the run.
- Fixed: up to nine site-wide promoted ads from unrelated categories were added to the results; an empty search returned them as nine rows. Only the page's own results are extracted now.
- Fixed: a category URL that Pazar3 does not recognise redirects to the all-listings page and used to be scraped as if it were that category. It is now skipped and reported (`INVALID_START_URL` when no valid URL remains).
- Fixed: `Max pages per URL: 0` now walks every page, up to the last page the site reports.
- Fixed: a run that reaches its maximum cost per run now stops there and finishes as Succeeded, instead of paying for more pages whose rows the platform discards and ending as Aborted.
- Faster: result pages are fetched 8 at a time and processed in order; a slow connection gets a second request on another IP. 1,000 listings in about 25 seconds.
- The run stops shortly before its own timeout (12 % of it, between 8 and 30 seconds) and keeps everything collected so far, so short API timeouts work too.
- The Node.js heap is capped at 70 % of the run's memory, so long exports are not killed for running out of memory.

### 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.
- Output verified on a live run: 406 row(s) across 14 columns, 99.9% of cells populated.
- Run reliability reviewed: 100.0% of public runs succeeded in the last 30 days.
- Input schema, output schema and pricing configuration reviewed.