Linkedin Jobs Scraper - PPR
Pricing
$1.00 / 1,000 results
Linkedin Jobs Scraper - PPR
Scrape jobs from linkedin jobs search results along with company details. Get key information to find contact info
4.7 (5)
Pricing
$1.00 / 1,000 results
255
Total users
4.7K
Monthly users
1.6K
Runs succeeded
>99%
Issues response
25 days
Last modified
2 hours ago
This (scheduled) run usually takes less than 30 minutes and costs less than $10. Today, having changed nothing to it, it's been running for over 2hs and hasn't finished yet, and it's already spent over $40
Open
This (scheduled) run usually takes less than 30 minutes and costs less than $10. Today, having changed nothing to it, it's been running for over 2hs and hasn't finished yet, and it's already spent over $40
Thanks for opening the issue, Let me check and get back to you
acendeo
Any news on this? Same thing happenned today
acendeo
?
Can you please share the run was finished as expected ?
Also the run you shared scraped around 61k jobs, so as per the fixed pay per 1000 result pricing, you would be charged $61 so you will not be charged more than you should be just because it took long time to finish
Also if we calculate the jobs scraped per minuted based on the time it took to scrape 61k results, the speed is around 200 jobs per minute which is also fast enough'
acendeo
It never finished, I had to abort it. It's impossible that there really are 61k jobs. The exact same run has been scheduled for months, and never had over 15k jobs. What changed?
acendeo
?
You have passed 157 search urls in a single run, each search URL can scrape upto 1k jobs, So definitely there is a possibility that it can scrape upto 157k jobs.
acendeo
Yes, but those exact settings have been there for over a month. And it never returned more than 15k jobs. Either LinkedIn changed something and the same URL does not scrape the same parameters, or the run is somehow broken. Since there are no mentions of changes on LinkedIn's side, I can only assume it's something on the actor's side. Are you going to investigate further or should I close this and look for another solution?
Is this issue solved ?
