Too many duplicates.. and always stopped after 2,000 records..

Hi,

We've resolved the duplication issue. Duplicates should no longer appear in your results. As for the actor stopping prematurely, that likely happens because you have maxLeads (Number of Leads per Input) set to 2000. If you need more leads, you can simply increase that setting. We don't currently support actor "resurrection," so increasing maxLeads is the best way to gather additional results.

Let us know if you have any other questions!

Caprolok

Hi,

Thank you for your quick reply. I haven't set the maxLeads per input to 2,000 but to one million (1,000,000), as shown in the attached image.

What could be causing this issue? Is there another place where I need to set that number of inputs?

I definitely don’t want the actor to stop, but it seems like it will anyway.

Thanks for your help!

Why did you close the conversation if the issues weren’t fully resolved?

I re-tested as you mentioned, and while there are fewer duplicates, they haven’t been completely eliminated. Out of 660 records, I still found 6 duplicates. The bigger issue is that after restarting the actor, I ended up with 1,293 records in total—523 of which were duplicates. That means I only gained 10 new unique records, bringing the total to 770.

Additionally, after your "fix," I set the input number to 50,000, but I only received 660 records, as mentioned earlier. This suggests that the "input number" feature is also not functioning correctly.

Your tool has a great potential and I would be happy to rent it, so could you please look into and try to resolve these issues?

Thank you for your help.

Hey there!

It looks like your issue was closed by mistake—sorry about that! Could you please share the run that triggered these duplicates? That information will really help us figure out what's going on.

Hi,

Thank you for getting back to me.

I've attached one of the configurations I tried, along with the last log file, which stopped at 660 results. I also tested other configurations—for example, selecting "no timeout," choosing the "last build," adjusting the number of leads, and keeping the keyword mostly the same (can I add multilple keywords to the same run?). As for the country setting, I either left it as default or selected the US, but the results remained the same.

Could you suggest a configuration that ensures the scraper won’t stop? Also, are you certain that your Apify scraping tool can run continuously without stopping? If that’s the case, I’d be happy to upgrade.

Looking forward to your guidance.

Thank you for your help. Best regards,

Hey @aerilyn454,

We’ve significantly enhanced the actor to be more robust and efficient than before. Here’s a quick summary of what’s new:

1. More comprehensive results: The actor can now run for a longer duration, so you can collect more data in a single run.
2. Actor resurrection: If you choose to resurrect the actor, please note that it will restart from the beginning rather than resuming from where it left off, meaning you will receive the same results as the last run.
3. Use synonyms for broader coverage: If you’re looking for similar results under different terms, try using synonyms of your keyword to expand your data set. Please note that you will need to start a new run with the synonyms.

We hope these improvements help you get the most out of the actor. If you have any other questions or run into any issues, just let us know—we’re here to help!

Best regards, Caprolok Team

Hi,

Thank you very much for all these improvements! I really appreciate that you are seriously developing your tools.

I tested the tool using the free Apify plan ($5.00 credit), and it ran without stopping, collecting 2,942 results, which is truly great!

Do you think this tool will allow me to collect up to 100,000 emails without stopping? Or do you know the limit before it stops? This is a crucial information for me to determine which Apify plan I should subscribe to, along with your Apify subscription.

Additionally, as feedback, I’d recommend finding a way to restart the actor from where it left off in previous runs. Right now, we are just scratching the tip of the iceberg, and we’re missing great data by not being able to dig deeper into the scraping process.

I appreciate your answers and look forward to your response.

Best regards,