crawlercrawler itself either using crawler.teardown()crawler.teardown() or crawler.requestQueue.drop()crawler.requestQueue.drop() (Not sure about this one), the main use case for it being saving on proxy costs/stopping crawlers from redundantly scraping data or even some other arbritrary conditions. shutdownshutdown flag in a state or even a variable and checking for it inside the handlers and if its true, just doing a return;return;(to empty out the queue) while this works it does add in a lot of noise in logs (also in the code) because we need to log that we are skipping them because of this flag for debugging purposes and I wish it would be handled a little more gracefully in the scraper instead of every request handler checking for itJoin the live workshop on Apify's Discord now for a hands-on demo with the team at Workato, and learn how to speed up your automation workflows with Apify. @everyone https://discord.gg/4fSg6MpdM
Saurav Jain · 2d ago
Hello @here 🙋♀️ Creator Cantina is starting in 5 minutes - I'll be there with <@566939201162051592> <@420988044531859468> and <@1555149962461970457> Come join us in #🧋creator-cantina - https://discord.gg/cgc64jbB4 to find out how Apify classifies Actors into categories and which ones are under/oversupplied to help you decide on your next project!
Eva · 6d ago
**Tasks are now limited to max 100 tasks across your account** Since published tasks get landing pages, and there are tens of thousands of Actors in Apify Store, the number of landing pages is increasing quickly. For now, we are limiting the number of tasks that can be published to 10 tasks per Actor, and a total of 100 tasks per account. More info here: https://docs.apify.com/actors/publishing/publish-task
ellativity · 2w ago
Join the Discord to ask follow-up questions and connect with the community