# Changelog of Substack Comments Scraper (`deriverge/substack-comments-scraper`) Actor

- **URL**: https://apify.com/deriverge/substack-comments-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/deriverge/substack-comments-scraper.md

##### 2026-10-11

*Fixes*

- `newsletterSubdomain` is filled for comments read through **Newsletters** and for newsletters on their own domain. Before, it was `null` there.
- Requests to Substack are paced. After HTTP 429 the actor waits as long as Substack asks, slows down, and if Substack keeps refusing, it stops and says so in the status message and `SUMMARY` instead of ending quietly.

##### 2026-09-30

*Fixes*

- Newsletters are read up to **Maximum posts per newsletter** even past their 23rd post. Until now a newsletter stopped after 23 posts because Substack's first archive page is shorter than the rest.
- In new-only mode, comments that did not fit under **Maximum rows** were remembered as seen and never sent. They now come with the next run.

##### 2026-09-23

*Features*

- First version: public comments and replies under Substack posts, from post links or from the newest posts of newsletters on `substack.com` or a custom domain, with the commenter's display name and handle, date, text, likes, reply count, `parentId` and `depth`.
- Three comment orders, a cap per post and per run, and a new-only mode that returns only comments that earlier runs under the same watch name did not.
