# Changelog of LinkedIn Top Content & Top Voices Scraper (`logiover/linkedin-top-content-scraper`) Actor

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

## Changelog

### 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: 100.0% 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

- 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.
- Declared 23 dataset fields from typed live cloud samples so the output contract is no longer an empty placeholder.
- Declared 23 nullable dataset fields from typed live cloud samples so the output contract is no longer an empty placeholder or brittle to sparse modes.

### 2026-07-18

- Maintenance & reliability pass — re-verified end-to-end against live data via the Apify API; confirmed the Actor completes successfully and returns non-empty, well-formed results within the 5-minute quality window on its default input.
- Refreshed build so the latest version is current; no change to inputs, output fields or scraping logic.

### 2026-07-12

- **Proxy support added** — page fetches now go through Apify Proxy (AUTO) with a fresh rotating IP per retry, and fall back to a direct connection on the final attempt. New `proxyConfiguration` input (defaults to Apify Proxy). This dramatically improves reliability against LinkedIn's rate-limiting; use the RESIDENTIAL group for very large runs.
- **Fixed proxy session-id crash** — the rotating proxy session id contained hyphens, which Crawlee rejects (`/^[\w._~]+$/`), causing every fetch to fail and the run to save 0 posts. Session ids are now hyphen-free, so the crawl actually fetches pages and returns data.
- **Category is now a dropdown** — the free-text category slug is replaced by a select of all 40 real LinkedIn Top Content directory topics (with human-readable labels), so users can't mistype a slug.
- **Time budget** — the crawl stops after ~4 minutes, saves everything collected so far, and exits successfully.
- **Graceful on blocks** — persistent blocks no longer fail the run; the actor logs a warning, ends the crawl, and exits success with whatever was collected.
- Empty input `{}` still works out of the box (defaults to the Marketing category) and returns curated high-engagement posts.
- Aligned the output schema link property to `results` for fleet consistency (dataset record field keys are unchanged).

### 2026-06-28

- Health check passed — actor verified working end-to-end on Apify platform.
- Changelog refreshed for Store quality compliance.

### 2026-06-20

- Maintenance & reliability pass: re-verified end-to-end against live data and confirmed the Actor completes successfully within the 5-minute quality window on the default input.
- Refreshed the prefilled example input and tuned run defaults for faster, lower-cost runs.