Facebook Pages Scraper avatar

Facebook Pages Scraper

Try for free

7 days trial then $20.00/month - No credit card required now

View all Actors
Facebook Pages Scraper

Facebook Pages Scraper

apify/facebook-pages-scraper
Try for free

7 days trial then $20.00/month - No credit card required now

Facebook scraping tool to crawl and extract basic data from one or multiple Facebook Pages. Extract Facebook page name, page URL address, category, likes, check-ins, and other public data. Download data in JSON, CSV, Excel and use it in apps, spreadsheets, and reports.

Do you want to learn more about this Actor?

Get a demo
RC

clay and apify

Closed

resolute_control opened this issue
4 months ago
RC

resolute_control

4 months ago

hi, just wanted to check in on this. Any input?

misa avatar

Hey, thank you for reaching out. Would you please share a run link/ID where you're experiencing this issue? Thanks!

lukaskrivka avatar

Hello,

Clay doesn't currently properly propagate the full error. The error can be seen in Developer Tools Console (opened F12 button). My hunch is that your Apify account doesn't have more RAM memory than 8 GB (free account) which means you can only run 2 runs at once.

We will be working with Clay to improve this flow but for now you will need to update the rows 2 at a time.

RC

resolute_control

3 months ago

Hi Lukas,

I’m currently using the free account.

A couple of follow up questions

  1. What’s the best way to run over 500 rows of data?  What’s your recommendation?
  2. Can it not queue up (i.e. run 2 then stop, then run another 2 then stop, etc…)?
  3. Where do you provide explanation about the RAM usage per run on apify?
  4. If I do upgrade to the next tier will I still be limited to 32 GB of memory (i.e. 8 runs at once in Clay).  We have over 500 rows in clay to run.

Thanks

lukaskrivka avatar

Hello,

These are great questions. I'm in contact with Clay so we hope to improve the integration asap with regards to question 1 and 2. If you could somehow put more rows underneath each other to a single run, that would solve the problem.

  1. If you click on the Actor that you want to run from Clay on Apify, you can see the default RAM on bottom in Run Options. Clay doesn't seem to allow lowering it.

  2. Yes, that's correct. Clay needs to make that easier.

RC

resolute_control

3 months ago

Hi Lukas,

Regarding the following: “If you could somehow put more rows underneath each other to a single run, that would solve the problem.”… what exactly do you mean by this? Can you be more precise in what you mean?

  1. I’m assuming by lowering the RAM, we can have more concurrent runs correct? If so, it doesn’t look like there’s an option to select the RAM in clay - https://prnt.sc/uM6xPD-YT30M. Where do you see the RAM within Clay? I can contact Clay myself to change this if I can show them this. Please send me a screenshot where you see the default RAM in Run Options within Clay.

Thanks

lukaskrivka avatar

Hello,

We are also in contact with Clay and proposed these changes. These suggestions that you mention will require bigger overhaul of their integration so I don't expect it will land very soon.

Developer
Maintained by Apify
Actor metrics
  • 712 monthly users
  • 50 stars
  • 100.0% runs succeeded
  • 19 hours response time
  • Created in Feb 2020
  • Modified 1 day ago