This changelog highlights releases that materially changed Instagram Comments Scraper for users. Dates use UTC; routine internal maintenance is omitted.
Fixes
- Runs no longer succeed silently with an empty dataset when no post could be loaded: if no requested post could be read and at least one failed to load, the run now ends as Failed with a clear message.
- Removed, private, or non-existent posts are now reported as unavailable in the run log, separately from temporary loading failures. The run status message summarizes comments, unavailable posts, and failed posts.
- Instagram server errors (for example HTTP 5xx or rate limiting) are always treated as temporary loading failures and retried, never reported as removed posts.
Changes
repliesCount is now null (unknown) instead of 0 when Instagram does not report a reply count; a partial reply preview is no longer used as the total. Instagram currently hides replies and reply counts from logged-out visitors; the README, the includeReplies input description, and the run log now state this limit.
Fixes
- Fixed the
sortBy option so popular returns collected comments by likes and newest returns them by timestamp, with deterministic tie-breaking.
Fixes
- Fixed
maxCommentsPerPost limits above the initial page, including 0, by following Instagram's logged-out comment pagination cursor when available.
Reliability
- Restored comment extraction after Instagram changed its embedded page data.
Features
- Launched on Apify Store for exporting public Instagram post comments with usernames, text, timestamps, likes, replies, and verification status.
