
Website Content Crawler
Pricing
Pay per usage

Website Content Crawler
Crawl websites and extract text content to feed AI models, LLM applications, vector databases, or RAG pipelines. The Actor supports rich formatting using Markdown, cleans the HTML, downloads files, and integrates well with 🦜🔗 LangChain, LlamaIndex, and the wider LLM ecosystem.
3.6 (39)
Pricing
Pay per usage
1403
Total users
54K
Monthly users
8K
Runs succeeded
>99%
Issues response
7.1 days
Last modified
10 hours ago
Adaptive crawler is failing to crawl the start URL
Closed
We are seeing the following error logs in some of our Adaptive Crawler runs:
2024-05-28T18:08:45.004Z ERROR AdaptiveCrawler: Request failed and reached maximum retries. mouse.wheel: Execution context was destroyed, most likely because of a navigation.2024-05-28T18:08:45.007Z at doScroll (/home/myuser/node_modules/@crawlee/playwright/internals/utils/playwright-utils.js:326:26)2024-05-28T18:08:45.009Z at async infiniteScroll (/home/myuser/node_modules/@crawlee/playwright/internals/utils/playwright-utils.js:337:9)2024-05-28T18:08:45.012Z at async genericHandler (/home/myuser/dist/request-handler.js:59:9)2024-05-28T18:08:45.015Z at async wrap (/home/myuser/node_modules/@apify/timeout/cjs/index.cjs:54:21)
We recently switched to the Adaptive crawler to avoid having to implement our own "fallback" logic of retrying crawls that failed with the Cheerio HttpCrawler
. Oddly, the website from this particular crawl usually succeeds with Cheerio so we're not sure why it's using the AdaptiveCrawler
.
Please let us know if there's something on our end we can do to fix this as we'd love to reduce the amount of custom logic and instead rely on the adaptive crawler

Dušan Vystrčil (dusan.vystrcil)
Thank you for using Website Content Crawler, and apologies for the delayed reply.
The error indicates that you are attempting to access data that has become obsolete or invalid due to Execution context was destroyed, most likely because of a navigation.
Unfortunately, we are unable to replicate the issue and therefore cannot provide further assistance at this time. If you encounter this error again, please let us know, and we will do our best to assist you.
I'm closing this issue, but feel free to ask any further questions.