# Changelog of Quora Scraper — Q\&A, Profiles & Spaces (`blackfalcondata/quora-scraper`) Actor

- **URL**: https://apify.com/blackfalcondata/quora-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/blackfalcondata/quora-scraper.md

## Changelog

All notable changes to Quora Scraper are documented here.

### 0.1.35 — 2026-09-01

#### Added

- "Most upvotes" is now available as a sort order, alongside "Relevance" and "Most recent". These are the three orderings Quora itself offers for answers.

#### Fixed

- "Most recent" now works. Sorting applies to the answers returned with each question, and asking for the newest ones previously had no effect on what came back. Search results themselves are still ordered by relevance, which is the only order this source offers, and the run log now says so instead of implying the whole result set was reordered.

### 0.1.33 — 2026-09-01

#### Fixed

- Choosing "Most recent" as the sort order no longer ends the run. Quora's search returns results by relevance only, and asking it for any other order made it reject the request outright, so every run that selected "Most recent" finished with no results at all. Those runs now complete normally, and the run log states that results came back ordered by relevance and that the time filter (for example "Past week") is the way to narrow to recent content.

### 0.1.31 — 2026-08-26

#### Fixed

- A run no longer ends on a single momentary fault from the source. A connection that drops part-way through a response, and a temporary error returned by Quora, now retry from a different network route instead of ending the whole run. Both were observed ending runs within seconds of the start, before a single result had been delivered, even though the very next attempt would have worked.
- A run that does fail now says in the run log what to try next, instead of reporting only an internal error code.

### 0.1.30 — 2026-08-16

#### Fixed

- A run that Quora refuses at start-up now retries from a different network route instead of failing outright. The refusal depends on which route the run happens to draw — the same page loads normally seconds later on another one — so a single refusal was ending runs that would have succeeded on the next attempt. A page that loads but no longer looks the way the actor expects still fails immediately, since retrying cannot fix that.

### 0.1.27 — 2026-08-01

- Enforce the published `maxResults` cap, including `0` for unlimited runs.
- Add one run-stable `scrapedAt` timestamp to every output record and dataset view.
- Remove inherited input fields that had no effect on Quora runs.
- Remove unreachable generic formatter, notification, and listing-template modules.

### 0.1.0 — 2026-07-12

- Initial release with questions, answers, profiles, posts, and Spaces by keyword or direct URL.
- Add pagination, result-type/time/sort controls, only-new-items mode, connected-app export, and structured dataset views.