Pay $0.30 for 1,000 tweets
🏯 Tweet Scraper V2 (Pay Per Result) - X / Twitter Scraper
Pay $0.30 for 1,000 tweets
⚡️ Lightning-fast search, URL, list, and profile scraping, with customizable filters. At $0.30 per 1000 tweets, and 30-80 tweets per second, it is ideal for researchers, entrepreneurs, and businesses! Get comprehensive insights from Twitter (X) now!
Allow me to reopen this issue, as the matter is not closed at all for me. I'm not interested in the explanation of why the problem happened. I still need to retrieve all data that contain the "createdAt" field as well as custom data that only contain the specific set of data including the field, but I can't.
My description of the problem:
I was able to save the "createdAt" field just a few days ago, but I can't any longer. I can clearly see the field in the browser window, but the field does not exist in the saved files in the csv and excel formats that I save. The field does not show up either in the window where you can specify the fields that you want to save. Thank you very much for reaching out! I just got the confirmation from our Engineering team. Seems like the actor is fetching this data piece but somehow Apify cannot generate the results. There are a couple of possibilities here:
The answer from the developer:
Apify cannot generate the CSV file properly. Therefore, it does not put the createdAt in it. Apify generates the CSV properly, but either Excel or CSV has a limitation on the columns. Which createdAt is over that limit. Because you already retrieved this data, and this data can be generated by clicking Storage -> Dataset -> Summary Data (In View section) -> Download as CSV
Hello again,
When I check your run, I can clearly see that the actor fetches the data with createdAt
property. However when you want to download it as an excel sheet, you don't see the createdAt
property right? This export functionality is an Apify functionality and is out of the scope of our actor.
Can you please reach out to Apify support and ask why export functionality is not working?
Thanks
Hey hey!
Closing due to the stale state. Please feel free to reopen the current issue, comment on this one, or create a new issue! We will always be here for you.
Cheers
- 1k monthly users
- 95.9% runs succeeded
- 0.29 days response time
- Created in Nov 2023
- Modified about 9 hours ago