All notable, buyer-visible changes to this Actor.
- Addendum: new Data Retention section right after section A (Architectural Disclosure). Names what Scrape Creators keeps and for how long (full response copies designed to expire within 31 days against the Publisher's account; request/usage/security/operational records with no fixed retention period per the provider's privacy policy; usage logs may be kept indefinitely). Also names the Anthropic surface when
enrichment or postSummary is on: comment and post text is sent under the User's own Anthropic API key and account, not the Publisher's; retention there is governed by the User's own agreement with Anthropic. Section letters A through M are unchanged; the new section is unlettered to avoid renumbering.
- Addendum section A, ToS Preamble bullet, and ToS section 6.1 bullet: add a one-sentence qualification right after each existing "does not store / log / retain" sentence. States that copies may remain temporarily in the Publisher's upstream provider accounts for the retention periods listed in the new Addendum section, after which the provider deletes them, and that the Publisher does not access these copies except where needed to troubleshoot a run at the User's request. No existing sentence removed; the original non-retention commitment stands verbatim with the qualification appended.
- Add Privacy requests section to the README with the Apify Issues tab route, a 30-day response commitment, and a plain statement that the actor keeps no copy of any comment data. Give privacy-request senders a real route and a real remedy (future-run block list).
- Add "What this actor deliberately does not return" to README Limitations — names the hard limits (no emails, phones, follower lists, inferred gender, reactor identity) so the deliberate narrowing of output is visible to buyers.
- README wording pass — swap three "Lead signals / high-intent commenters / lead-gen fields" phrases for "Audience research" equivalents. The old phrasing proposed a cold-outreach use that Scrape Creators' own acceptable-use policy forbids.
- Remove
sortBy input (BREAKING). The upstream Scrape Creators API has no sort parameter, so sortBy: 'newest'/'oldest'/'most_reactive' was implemented client-side by buffering every upstream page before sorting — on large posts this burned upstream API credits for a buyer-set cap that only applied after the full fetch. Comments now stream live in Facebook's default upstream order under all circumstances. Impact on saved Tasks: any Task passing sortBy other than 'top' will no longer get sorted output on its next run; it will get Facebook's default order instead. The input itself is removed, so existing values are ignored silently rather than failing validation.
- Hoist
commentsNewerThan empty-page auto-stop so it always runs. Previously the 15-consecutive-empty-pages safety net lived inside the buffered-sort code path only. With that path gone, the guard now runs for every run that sets commentsNewerThan, so an old post hit with a recent date no longer walks every upstream page.
- Free-plan cap lowered from 50 to 5 results per run. Free Apify users now get up to 5 items per run (down from 50). Paying users are unaffected. Description, README and input-schema help text updated to match.
- Rewrite README product-facing top. Restructured around buyer questions ("What do I paste in?", "What comes back?"), added an honest Limitations section, trimmed FAQ from 20 to 10 highest-value questions. Terms of Service untouched.
- Sync
.actor/actor.json with Apify Console. Title, description, keywords, and categories in the repo now match what buyers see on the store page. Added AUTOMATION category and 4 new keywords (facebook reels comments, no cookies scraper, per-reaction breakdown, feedback id).
maxComments and maxRepliesPerComment default to 0. 0 now means "all available" — pagination runs until upstream reports no more. Any positive value still caps as before. Free-plan 50-item cap unaffected.
- Remove
excludeAuthorGender input. The inferred author.gender field is now always stripped from output. Removes a sensitive-adjacent field unconditionally, no opt-in required.
- Fix replies-stage HTTP 400. The upstream replies endpoint requires both
feedback_id and expansion_token from the parent comment — every reply fetch was failing before this. Added a regression test.
- Surface upstream response body in error messages. HTTP failures now include a sanitized snippet of the upstream body (API key + credit/quota/billing/plan/usage/account fields redacted).
- Combine
postUrls + feedbackIds into one input. Paste URLs, feedback IDs, or a mix in the same field. The Actor auto-detects each entry — URL if it starts with http(s)://, else feedback ID.
- Additive Related-actors section in the README (5 keyword-anchored cross-links inside the UnseenUser Facebook + cross-platform toolkit).
- Additive Demo video section in the README (embedded Apify scheduling and integrations walkthroughs).
- Restored the output schema — run page now shows a dataset view + run summary card.
- 10-task SEO audit + tightening across the task portfolio (per-task titles, per-task SEO descriptions).
- Additive SEO enhancements to README's marketing zone (input examples, output shape, related actors, FAQ expansion).
- Initial 1.0 release. Facebook post and reel comments with the full 10-type per-reaction breakdown (thankful, like, love, care, haha, wow, sad, anger, pride, confused), threaded replies on demand, error rows as first-class dataset entries with a
stage discriminator, and three prebuilt dataset views (comments overview, per-reaction breakdown, errors).