Wellfound Premium Jobs Scraper
Pricing
$24.99/month + usage
Wellfound Premium Jobs Scraper
Extract data like job title, description, salary range, location, job link and company socials. Specify the search based on job title, location or customized via URL. Supports search and URL lists. Download your data as HTML Table, JSON, JSON-L, CSV, Excel, XML, RSS
4.4 (5)
Pricing
$24.99/month + usage
20
Total users
359
Monthly users
86
Runs succeeded
>99%
Issues response
6.8 hours
Last modified
4 days ago
Scraper stops with error
Closed
Hi!
Unfortunately the scraper sometimes stops with this error "ERROR We are sorry, this should not have happened. Please report this issue to us with your run at https://apify.com/radeance/wellfound-job-listings-scraper/issues/open"
Hi @s.gigel, thanks for reporting this!
We’ve looked into the run you shared, and it seems like the error was likely caused by a data validation issue. We’ve just pushed an update to help mitigate these kinds of cases going forward.
Also, just a quick check — did you set the timeout to 3600 seconds as suggested by the run? With larger queries like the one in your run, a longer timeout is important to ensure the process completes smoothly.
If anything else comes up or if you run into further issues, feel free to reply here — we’re happy to help!
s.gigel
Yes, 3600 timeout is set by default
Now I'm experiencing this error "2025-06-24T13:38:40.607Z [apify] ERROR Unexpected error while processing job listings due to: 'NoneType' object has no attribute 'cookies'"
Hi @s.gigel, Thanks for the update!
To help us debug the new error ('NoneType' object has no attribute 'cookies'), could you please share the Run ID where it occurred? That will allow us to pinpoint exactly what went wrong and resolve it quickly.
Also, just a reminder: for larger queries, it’s important to set the timeout value higher in the run options. If the timeout is exceeded, the actor execution will stop prematurely, which can lead to incomplete results or unexpected errors.
Looking forward to your reply!
s.gigel
run id is a5eTZymnpAv2ZOg3q
so I need to set the timeout even higher? 7200+?
Thanks
Hi @s.gigel,
Thanks for the update and for sharing the run ID.
I checked the run and the issue was actually unrelated to the original one — but good news: it’s now fixed on our end.
Also yes, if your runs take close to an hour, it’s best to increase the timeout. Setting it to 7200 seconds (2 hours) should give the Actor enough breathing room for larger queries.
One more important note: We recently noticed 403 blocks happening for some users due to ip blocking on Wellfound’s side. To mitigate this, we recommend switching to the Residential Proxy – Region: United Kingdom. You can change this under Advanced Options in the Input tab on the Actor page. It will be the default from now on when you reset your input.
Let me know if anything else comes up!
