I see that every run your scraper registered 2 runs. something is not right!

Hi Nirheu,that’s a really good observation, and I totally understand why it feels confusing.

I just tested the actor again on my side, and I didn’t see the double-run issue you mentioned.

Would it be possible that there are two different actors or overlapping task triggers in your setup?

If you can share the input URL or a bit more about how you’re triggering the actor, I’ll personally run it in my environment and help you confirm exactly what’s going on.

Thanks for the example! To help me check more accurately, would it be possible to send me the 2 URL of the specific run from your Apify dashboard? That way I can look into the exact case for you.

I know it might take a moment, but could you please send me both the run ID and the run URL?

You can just click into the run on your Apify dashboard, then copy the page link and the run ID shown there. That would help me a lot!

Hello Bro~ thanks for sharing the run ID — really appreciate it!

Right now I can’t access the run data yet. Could you please go to Settings → Share run data with developers and make sure my actor is selected there? That way I’ll be able to view the details.

Also, would you mind testing one more time using this URL: https://apify.com/pricing? Once that’s done, I can access the data and check exactly what’s going on.

Hello bro! I looked into the issue and found the two runs by matching the 27s duration and timestamp. They have different execution times, so it looks like they were two separate tasks — not a duplicate run.

I also noticed the actor was triggered via API, so it’s possible the issue came from the API call itself. You can try running it directly from the Apify dashboard to verify. I’ve also been testing an online tool that uses this actor’s API, and haven’t seen any duplicate runs so far.

I tested your original actor using the same URL on Apify, and only one run appeared.

Anyway, if you need to scrape a specific URL, I suggest using my latest actor here: https://apify.com/6sigmag/fast-url-content-crawler

It’s designed to extract full content from exact URLs, while the previous one only targets homepages.

Hope this clears things up!

Great observation — the difference in character count makes total sense.

The two actors are designed for different goals. If you’re trying to quickly filter leads, scraping just the homepage is often enough and much faster. But if you need deeper analysis or want to feed more accurate text into your AI model, the exact URL actor is better — it focuses on full text from that specific page and skips unrelated content.

I’d also love to improve the tools further. Would you mind sharing a bit about how you plan to use the data? That way I can make future updates more useful for your case.