# Changelog of LinkedIn Company Scraper: Details, Posts & Jobs (`danthedataman/linkedin-company-activity-ledger`) Actor

- **URL**: https://apify.com/danthedataman/linkedin-company-activity-ledger/changelog.md
- **Full Actor documentation**: https://apify.com/danthedataman/linkedin-company-activity-ledger.md

## Changelog

### Unreleased

- Optional `maxRunSeconds` run time budget (default 210 s, 0 disables): once it is reached, no further two-company batch starts; the batch in progress finishes, and companies not started are listed in ERRORS and are not charged. This keeps typical long lists inside Apify's 300-second default run timeout.

### 90.15

- Optional `cacheMaxAgeHours` (0-720) reuses pages this Actor read in your earlier runs, kept in a key-value store in your own account. Omitted, null or 0 reads every page live. Every row carries `scrapedAt` and `cached`. Cached rows are billed like live rows.
- Base image pinned by digest; Python dependencies pinned with a constraints file.
- A company's requested facts and jobs are no longer lost when its public Updates are missing or unreadable (no Updates, or an Update card without its activity ID or with an unexpected post URL). When posts were requested, ERRORS records them as absent with the reason. Such a page is not cached.

### 0.2

- Fresh company sessions and bounded concurrent root reads.
- LinkedIn's stated employee and follower counts, About text, company type, founded year when shown, all delivered offices and related pages.
- Per-attempt timing lines in the run log (request type, attempt, status, session setup, pacing wait, request seconds; no URLs).
- Store README rewritten buyer-first, with speed, phone, funding and employee-statistics limits stated.
- Anonymous browser fallback uses the same row contract and reports its read count in the run summary.

### 0.1

- Joined public company facts, recent root Updates and organization-filtered guest job cards.
- Read-only snapshot baseline for new post/job identities; current facts remain available.
- Paced datacenter sessions, login-wall/999 rotation, separate ERRORS and charge-limit stopping.