Facebook page posts checker
30 days trial then $39.00/month - No credit card required now
This Actor may be unreliable while under maintenance. Would you like to try a similar Actor instead?
See alternative ActorsFacebook page posts checker
30 days trial then $39.00/month - No credit card required now
Facebook page checker extracts posts until several years from past, reviews and page details. Groups added as beta, less posts expected but with better details.
Do you want to learn more about this Actor?
Get a demoFacebook page posts checker api sometimes skips posts
Closed
Dear Apify!
We ran into some problems while using the Facebook page posts checker api.
We executed 2 consecutive runs for the same facebook page:
run 1 Id: VuWjBXu4VhdBpPeCm run 2 Id: od5GkE4ipc4M7cPvc
The only difference between the inputs of the two runs was that the time interval of the second run was one day longer. So the expected result was, that the second run should find more posts, since it covers a bigger time interval, and it completely covers the time interval of the first request.
Against our expectations, the first run gave us 16 posts, the second gave only 13. The posts numbered 11 to 15 from the first run were missing from the results of the second run.
The state of the second actor was "Succeeded - Actor finished successfully (exit code 0)", but in the actor logs we have found the followings:
WARN CheerioCrawler: Reclaiming failed request back to the list or queue. request timed out after 30 seconds. And a JS error: Error at Function.createFromInputFallback (/usr/src/app/node_modules/moment/moment.js:324:25)
Questions: 1, Can you confirm, that this is a bug, that the Facebook page posts checker api sometimes skips posts, and it will be fixed?
2, Looking at this case, since the state of the run is "succeeded", our only chance would be in production to automatically catch this error and rerun the request, if we would query and process the logs automatically after each run, looking for warn or error lines. Is it recommended for clients by the Apify team to investigate the logs after each request, or can we expect, that the state of the finished run reliably reflects the occurence of an error?
Hey, we no longer support this Actor, although we know it still works well for some users. We have upgraded to new "Actor line", you can give a try to one of those, https://console.apify.com/store?search=face, for example the https://apify.com/apify/facebook-posts-scraper.
Apify- 19 monthly users
- 12 stars
- 99.8% runs succeeded
- 8.8 days response time
- Created in May 2022
- Modified 4 months ago
