# Changelog of Facebook Comment Scraper (`dz_omar/facebook-comment-scraper`) Actor

- **URL**: https://apify.com/dz\_omar/facebook-comment-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/dz\_omar/facebook-comment-scraper.md

## Changelog

All notable changes to the Facebook Comment Scraper.

### 2026-09-07

#### Added

- **Max replies per comment.** A new input that caps how many replies are pulled from each
  top-level comment. Reply counts on Facebook are wildly uneven — most comments have none,
  while a single popular one can carry 80+ replies — and those few threads used to dominate
  both the run time and the size of your bill. Set it to keep a run predictable, or leave it
  at `0` for unlimited (the previous behaviour, unchanged).

#### Improved

- **Runs cost significantly less.** Data is now transferred compressed end to end, cutting the
  bandwidth a run consumes by roughly 70%.
- **More posts scrape successfully.** Reels, photos and page posts that previously returned
  "could not retrieve comments" now succeed. The actor recognises when Facebook has served it
  a stripped page and retries properly instead of giving up on that URL.
- **Fewer wasted retries.** A failing URL no longer spends minutes cycling through repeated
  attempts before reporting back.
- **Runs no longer stall.** A request that Facebook accepted but never answered could leave a
  run hanging until it hit its timeout, returning nothing for that URL. Requests are now
  bounded and retried, so a stalled request costs seconds instead of the whole run.

#### Fixed

- **Run summary reported the wrong authentication state.** Runs without cookies were labelled
  "Authenticated" because Facebook hands anonymous cookies to every visitor. The summary now
  reports authentication only when a real logged-in session is supplied.
- **Interrupted runs resume correctly.** If a run is migrated, aborted or restarted, it now
  picks up from its last checkpoint instead of starting over, and results already delivered
  are never delivered — or charged — twice.
- **Spend limit is respected exactly.** A run stops precisely at the maximum cost you set, and
  never delivers results it has not charged for.

#### Changed

- **Pricing.** Comment results are cheaper, replies are priced closer to what they actually
  cost to collect, and platform usage is no longer passed on to you — the per-event prices are
  now the whole bill. See the pricing section on the actor page for the current rates.