# Changelog of Threads Scraper - Scrape threads.net Posts, No Login (`logiover/threads-scraper`) Actor

- **URL**: https://apify.com/logiover/threads-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/logiover/threads-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.
- Output verified on a live run: 18 columns returned, 77.6% of cells populated.
- Run reliability reviewed: 99.5% of public runs succeeded in the last 30 days.
- Input schema, output schema and pricing configuration reviewed.
- Noted that 2 column(s) came back empty in this sample (`lang`, `hashtags`); these are under review.

### 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-12

- Runs are now roughly 250x cheaper. Measured on identical input: $0.6011 → $0.0024.
- Switched the default proxy from the RESIDENTIAL group to datacenter. Threads does
  not block datacenter IPs — verified side by side, both tiers return the same posts
  and datacenter is faster. A proxy is still required; direct requests get an
  interstitial. Residential remains available and is used automatically if datacenter
  ever fails to return a usable page.
- Profile pages are now read over plain HTTP first. The browser pass is kept only as a
  fallback for when HTTP returns nothing, so most runs no longer launch Chromium at
  all — faster, lighter, and without the intermittent proxy tunnel failures.
- Restored profile scroll depth and patience that had been cut to save bandwidth.
- More retries before changing proxy tier, so a single transient failure no longer
  pulls an entire run onto the expensive path.

### 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 18 dataset fields from typed live cloud samples so the output contract is no longer an empty placeholder.
- Declared 18 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

- Empty input now returns data: with no usernames / post URLs / search terms, the Actor browses a popular public profile plus a broad trending search and returns a bounded batch of recent posts (no more "provide at least one target" error).
- Bounded the zero-input run (defaults to 200 posts) so it stays fast and cheap; explicit runs can still set `maxResults` to 0 for unlimited.
- Made the "no valid targets" path exit cleanly (log + success) instead of hard-throwing and failing the run.
- No output field keys changed; numeric fields (likes, replies, reposts, quotes) remain real numbers.

### 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.