Facebook Posts Scraper V2 avatar
Facebook Posts Scraper V2

Pricing

$1.00 / 1,000 posts

Go to Store
Facebook Posts Scraper V2

Facebook Posts Scraper V2

Developed by

Axesso - Data Service

Axesso - Data Service

Maintained by Community

Our Facebook Posts Scraper extracts real-time posts from Facebook, including text content, images, timestamps, engagement metrics, and other key details. Download the data in formats such as JSON, CSV, Excel, XML, or HTML. Use time ranges to define the period for which posts should be fetched.

0.0 (0)

Pricing

$1.00 / 1,000 posts

5

Total users

134

Monthly users

79

Runs succeeded

>99%

Issues response

9.4 days

Last modified

2 months ago

WC

facebook-posts-scraper-v2 actor returns 500 error for valid Facebook page IDs

Open

woundless_corner opened this issue
10 days ago

Dear Apify Team,

I am using the facebook-posts-scraper-v2 actor in production and have encountered an issue where the actor consistently returns HTTP 500 Internal Server Error for certain Facebook page IDs, even though these pages are active and publicly accessible.

Here are the details of the issue:

Actor: axesso_data/facebook-posts-scraper-v2

Affected Page IDs:

102602877789428

161882950552820

API Request Parameters (example):

json Copiar Editar { "pageId": "102602877789428", "startTime": 1752862018, "endTime": 1752861418, "maxPosts": 50 } Observed Behavior:

The actor initializes normally and attempts to fetch posts.

It retries twice after receiving 500 errors from the Facebook API but fails completely with the following logs:

bash Copiar Editar Error fetching data for page id 102602877789428: 500 Failed to retrieve data for page id 102602877789428 after 2 retries. Returned status code 500 No posts are retrieved for these pages, while other pages in the same run work as expected.

Checks performed:

Verified that the Facebook pages are publicly accessible.

Manually checked that the pages have recent posts.

Confirmed that other page IDs are processed successfully in the same actor run.

Request: Could you please investigate why these valid page IDs are causing 500 errors? Is it related to specific page settings or API limitations? Are there any recommended parameter adjustments or workarounds to prevent this issue?

Thank you for your support.