Twitter Tweet Reply Scrape | $0.25/1K Tweets | Pay-Per Result avatar

Twitter Tweet Reply Scrape | $0.25/1K Tweets | Pay-Per Result

Try for free

Pay $0.25 for 1,000 Tweets

Go to Store
Twitter Tweet Reply Scrape | $0.25/1K Tweets | Pay-Per Result

Twitter Tweet Reply Scrape | $0.25/1K Tweets | Pay-Per Result

kaitoeasyapi/twitter-reply
Try for free

Pay $0.25 for 1,000 Tweets

🚀 Instantly scrape Twitter/X replies & conversations with Pay only $0.25/1K tweets. Get complete reply chains, user info & engagement metrics. Perfect for sentiment analysis, market research & competitor tracking. 100% reliable data extraction, no API needed!

HR

Running for an hour with no result output

Closed

hrukalive opened this issue
7 days ago

I started the actor with about 800 conversation IDs. Although the log shows constant output with a changing cursor, no data is outputted after an hour of running time. Eventually, the actor runs out of memory.

HR

hrukalive

7 days ago

I have tested with a smaller number of conversation IDs, and it seems to have worked. Are the crawled data temporarily saved in RAM rather than written out?

KaitoEasyApi avatar

Get it. We will check. Thanks for feedback.

KaitoEasyApi avatar

Sorry ,I can't open the run link.

You can touch me by

  1. https://x.com/kaitoEasyApi
  2. https://t.me/kaitoeasyapi
HR

hrukalive

7 days ago

Sorry, I have to clean up the tasks, but my general observation is that the result seems to be written out at the end of the crawling, which is causing the usage with too many conversation IDs to be impractical unless with a large enough RAM.

KaitoEasyApi avatar

Yes, your guess is correct. Currently, the data is only written to the file at the very end. I'll look into how to optimize this process. In the meantime, if you need to retrieve the data, you can make multiple requests with a reduced number of conversations each time. Best regards.

HR

hrukalive

6 days ago

Thank you.

Developer
Maintained by Community

Actor Metrics

  • 18 monthly users

  • 3 stars

  • 88% runs succeeded

  • 3.3 hours response time

  • Created in Dec 2024

  • Modified 5 days ago