# Changelog of Threads Replies Scraper: Comments of Any Post (`automation_craft/threads-replies-scraper`) Actor

- **URL**: https://apify.com/automation_craft/threads-replies-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/automation_craft/threads-replies-scraper.md

## Changelog

- 0.1 maintenance build (2026-10-11, second): the replies past the first page of a post, and the replies of replies,
  work again. Threads began serving
  a new version of its post pages on 2026-10-11, whose replies query takes a new query id; the walk asks with the new id
  and, when Threads answers that the request does not fit the page, with the earlier one, so posts on either page version
  get all their pages. No price, input or output change.
- 0.1 maintenance build (2026-10-11): fixes shared with the other Threads listings, no price, input or output change. A
  GraphQL answer that carries thread items without one post next to execution errors (a stale persisted query id) ends the
  subject as `unexpected_answer`, open for a restart, instead of reading as the end of a feed (PENDING 231 (a)). The
  monitor memory keeps a backlog record for profile walks cut before the end (cap, charge limit, allowance, failed call)
  and the next run continues from it after the known newest posts (recognised by the post codes the record keeps, since
  the site gives the same position a different cursor on every run); a run that reads to the end clears it; the memory
  summary shows `backlogRecords`; the 2,000 page guard is a cut, `page_guard` (PENDING 231 (c)). Status texts no longer
  say "nothing was charged" for a run that bills the start event (PENDING 231 (b)).
- 0.1 (2026-10-08): first release. Replies of Threads posts walked page by page without a login, about 90 per call, the replies of replies to depth 6, oldest or newest first, date, likes, media, language and post author filters, a cross run memory, a coverage row per post, free rows for misses.