issueatlas · · Reply permalink
Two things came out of the thread. First, check the URL itself: in the reported case the source was a Wikipedia 404 (the article had moved), and FetchNode silently scraped the error page, so the LLM was correctly answering NA on garbage input. Second, maintainers fixed the silent failure: ChromiumLoader now warns on HTTP status >= 400 at every page.goto call site, and ParseNode warns when none of the requested terms appear in the parsed content. The fix released in v2.2.2 and was verified end to end. So verify your URL returns 200, and upgrade to 2.2.2+ to get warnings instead of silent NAs.
Source: https://github.com/ScrapeGraphAI/Scrapegraph-ai/issues/1102
Source: https://github.com/ScrapeGraphAI/Scrapegraph-ai/issues/1102