Amazon Reviews Scraper with Advanced Filters
Pricing
$35.00/month + usage
Amazon Reviews Scraper with Advanced Filters
This Amazon Reviews Scraper is designed to extract a vast amount of reviews (up to tens of thousands) for a specified ASIN with high efficiency. By utilizing advanced review filters, it ensures that you capture as many relevant reviews as possible.
3.7 (2)
Pricing
$35.00/month + usage
52
Total users
454
Monthly users
89
Runs succeeded
>99%
Issues response
2 days
Last modified
5 days ago
Duplicate Runs
Closed
Input: {"ASIN_or_URL":["B0BXYVM5PF","B0BXYS7RWL"],"End_date":"2025-04-13","country":"United States","filter_by_mediaType":["all_contents"],"filter_by_ratings":["all_stars"],"filter_by_verified_purchase_only":["all_reviews"],"max_reviews":100,"recent_days":0,"sort_reviews_by":["recent"],"unique_only":false,"filter_by_keywords":[]}"} Issue Description :white_check_mark: Working Scenario: When the job is triggered once in isolation, the system behaves as expected: The actor processes the input correctly. A single job is executed internally. The output is deterministic and aligns with the expected result. :x: Failing Scenario: When the job is triggered concurrently with identical input: The actor receives multiple simultaneous job requests. Despite the input being identical, the actor's internal state is mutated unexpectedly due to concurrent access or race conditions. As a result: The input payload is altered mid-execution. The actor spawns multiple internal jobs even though only one request should be processed. The output becomes inconsistent or non-deterministic, returning random results across executions. :test_tube: Technical Analysis (Hypothesis): The actor is likely stateful and not thread-safe. Shared mutable state is being accessed or modified without proper synchronization mechanisms (e.g., locks or message queues). The job scheduling mechanism might be reentrant or failing to enforce idempotency, leading to duplicate execution paths for a single logical request. :hammer_and_wrench: Potential Fixes to Explore: Introduce a job deduplication mechanism or guard clause to prevent reprocessing of the same input concurrently. Refactor the actor to ensure statelessness or make it concurrency-safe using appropriate synchronization techniques. Implement input immutability and deep-copying to protect shared data from side effects. Review actor lifecycle management and ensure only one instance handles a given input at any time.
Hi, Amazon has recently updated their risk control strategies. I'll investigate appropriate measures and expect to resolve the issue within three business days.
Hi, the issue in the U.S. region has been resolved and everything is working normally now. Other regions will gradually recover within the next three days. Thank you for your patience.
