# How do you handle HTTP 429s when running daily price checks in Apify?

I’m using a custom Apify Actor to collect public Meta Quest prices for daily catalog checks, and each run outputs a dataset for price comparison. The run logs are helpful for spotting failed requests, but during larger runs some pages returned HTTP 429. Switching to a US proxy fixed the issue on the pages we retested, though residential proxies feel fairly expensive. What approaches have worked for you to reduce 429s without driving up proxy costs?

##### Post Metadata
- Posted at: 3 days ago
- Author title: AI Product &amp;amp; Integration Lead
- Net upvotes: 1



## Related Product
[Apify](https://www.g2.com/products/apify/reviews)

## Related Category
[API Marketplace](https://www.g2.com/categories/api-marketplace)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4


