
TikTok Scraper
Pricing
Pay per event
Go to Store


TikTok Scraper
Extract data from TikTok videos, hashtags, and users. Use URLs or search queries to scrape TikTok profiles, hashtags, posts, URLs, shares, followers, hearts, names, video, and music-related data. Export scraped data, run the scraper via API, schedule and monitor runs or integrate with other tools.
4.4 (23)
Pricing
Pay per event
460
Total users
44K
Monthly users
10K
Runs succeeded
98%
Issues response
1.4 days
Last modified
2 days ago
Job start with uncaught exception
Closed
Synthesio opened this issue
a year ago
Hello,
Since this morning we have some failed job with this error at the start of the scraping
Example:
2024-07-30T13:19:46.135Z ACTOR: Pulling Docker image of build aB2N9dRICpmpHeyoo from repository.2024-07-30T13:19:46.259Z ACTOR: Creating Docker container.2024-07-30T13:19:46.363Z ACTOR: Starting Docker container.2024-07-30T13:19:47.722Z Starting X virtual framebuffer using: Xvfb :99 -ac -screen 0 1920x1080x24+32 -nolisten tcp2024-07-30T13:19:47.723Z Executing main command2024-07-30T13:19:51.940Z INFO System info {"apifyVersion":"3.2.2","apifyClientVersion":"2.9.3","crawleeVersion":"3.10.4","osType":"Linux","nodeVersion":"v20.15.1"}2024-07-30T13:19:53.974Z INFO Starting the crawler.2024-07-30T13:19:54.581Z INFO Will discard all profile posts older than Thu Jul 25 20242024-07-30T13:19:55.680Z INFO PlaywrightCrawler: Starting the crawler.2024-07-30T13:19:57.573Z node:internal/process/promises:3912024-07-30T13:19:57.575Z triggerUncaughtException(err, true /* fromPromise */);2024-07-30T13:19:57.576Z ^2024-07-30T13:19:57.577Z2024-07-30T13:19:57.578Z page.evaluate: Execution context was destroyed, most likely because of a navigation2024-07-30T13:19:57.578Z at Page.<anonymous> (/home/myuser/dist/src/tools/api/web/web-api-signer.js:105:24) {2024-07-30T13:19:57.579Z name: 'Error'2024-07-30T13:19:57.579Z }2024-07-30T13:19:57.582Z2024-07-30T13:19:57.583Z Node.js v20.15.1
Thx

Sviatozar Petrenko (svpetrenko)
a year ago
Hi, thanks for notifying! We've rolled out some fixes that should handle this. Let's keep it open for some time to see it doesn't happen again