Web scrapers returning the same data for different URLs

[OrionSeven]

Hi,

My loop has two web extractors in it.

In the first it gets passed the url https://www.thehackernews.com.

The second gets passed the URLhttps://thehackernews.com/search?updated-max=2025-07-09T14:10:00%2B05:30&max-results=12. This is the link to page 2 of the news.

When I run the flow they both end up with the same website content, even though they have two different URLs

I thought it was an issue with the site. But when I use the links with CURL, I get different content as expected.

What’s going on?

https://www.gumloop.com/pipeline?workbook_id=xir9wbPRz5rqMgJwe8sn3S

[Gumloop_Bot]

Hey @OrionSeven! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.

1. Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}

2. Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
   

3. Provide details about the issue—more context helps us troubleshoot faster.

You can find your run history here: https://www.gumloop.com/history

[Wasay-Gumloop]

Hey @OrionSeven – Thank you for flagging, that is indeed strange. I’ll investigate further.

cc: @Arslan Would you be able to look into this when you get the chance please? https://www.gumloop.com/pipeline?workbook_id=sPuHM81h9qUNdE9kdBsGCV&run_id=jdCZDLFYXuEPoYTdfvdvte

tldr: The root URL is being scraped instead of the paginated URL.

[Arslan]

Hey @Wasay-Gumloop thanks for reporting the issue, I’ve identified the problem and will be deploying a fix in the next few hours

[Arslan]

Hi @OrionSeven,

The issue is now fixed, it was due to an issue in decoding the query parameters that were responsible for the pagination. Sorry for that, thanks again for reporting. Let me know if you run into any other issues or have questions!

(cc: @Wasay-Gumloop)

Best,
Arslan