# Changelog of Skip Tracer — Address History & Relatives Finder (`0xgollum/skip-tracer`) Actor

- **URL**: https://apify.com/0xgollum/skip-tracer/changelog.md
- **Full Actor documentation**: https://apify.com/0xgollum/skip-tracer.md

## Changelog

### 0.2.11 — 2026-10-08

- **Run time capped.** The search fetch now has a hard 170 s budget. When one source (ThatsThem) sat behind an anti-bot wall, retries plus challenge waits held the run for 8-9 min even though another source had answered in under a minute — which also made Apify's 5-minute automated quality test fail and flagged the Actor "Under maintenance". Whatever was fetched in time is still parsed and returned.

### 0.2.x — Cold review (09/09/2026)

- A no-match / blocked run pushed a `status` row to the dataset, i.e. a billed item on a run that returned nobody — contradicting "zero matches never billed". The status now goes to the run key-value store (`LAST_RUN_STATUS`).

### 0.2.10 — 2026-08-28

- New optional input **`include_contact_details`** (off by default). When on,
  the Actor also opens each matched profile's detail page to pull **phone
  numbers, emails and full street addresses**. This roughly doubles run time
  (one extra browser page per profile) and is strictly time-bounded — if a
  detail page is blocked or slow, that profile just comes back at search level
  and the run still succeeds. Leave it off for a fast address-history /
  relatives lookup.

### 0.2.7 — 2026-08-28

**Fetching rebuilt on a real browser — the Actor returns results again.**

- The people-search sources had hardened their bot protection to the point
  where plain HTTP requests were fully blocked (403 on every request), so the
  Actor was returning nothing. Fetching now runs on a real headless Chromium
  with realistic browser-fingerprint injection and automatic session
  rotation, which gets past the challenge.
- **Runs take longer than before** (roughly 1–4 minutes) because the browser
  has to load each page and ride out the anti-bot check, with retries on a
  fresh session when one is blocked. In exchange, you get real records back.
- TruePeopleSearch is the primary source and comes through reliably;
  FastPeopleSearch is used when it clears; ThatsThem is frequently
  unavailable. Partial results from whichever sources responded are still
  merged, scored and returned.
- Phone numbers / emails live on the per-profile detail pages and are not
  fetched yet — current output is name, age, current + previous locations,
  relatives and the profile link.
- Default run memory raised to 2 GB (Chromium needs the headroom).
- Every run returns at least a `status` row (never an empty, failed-looking run).

### 0.1.x / 0.2.x — 2026-07 → 2026-08

- Multi-source skip tracing (name / phone / email / address) with clustering,
  confidence scoring, relatives and address history; per-query isolation.