Facebook Pages → Watch Posts module

:bullseye: What is your goal?

Facebook Pages → Watch Posts module

:thinking: What is the problem & what have you tried?

This module has been working fine, but since today an error started appearing. I’ve already tried recreating the connection, but the same issue persists and it also happens in different scenarios.

:clipboard: Error messages or input/output bundles

Handled error
type ConnectionError
message [500] The external server cannot process the request due to an internal issue.
Details:
Please reduce the amount of data you’re asking for, then retry your request (1, )

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

Hi @nunorsr

The HTTP error 500 is a server side error and generally there isn’t much we can do about it, but wait until it’s fixed on their side. Check out this answer for a possible retry mechanism.

However, the error message you get carries an important piece of information.

Since you noticed that the scenario was running fine and this started to happen after a while, I believe this is one of those “time-bomb” issues, where things go well in the beginning and tend to fail when the volume of data grows. The error message kind of confirms that.

Also, since you’re watching posts on a page, that assumption makes sense, since the number of posts tends to increase over time without your control.

This, use the limit field to retrieve a smaller number of posts. As an alternative, combine that with right clicking the module and selecting “Choose where to start” to restrict the results even further.

@damato

1 Like

@nunorsr did you find any solution? I’ve got the same error for my lasts executions, I tried to create a new connection and even set the limit to 1 but it doesn’t make a difference.
I wonder if anyone has figured it out a solution or workaround. Could this be a Make issue @damato ?

Thanks

I tried to solve it, but even when manually selecting the post, the same error occurred. Even when I set the limit to 1 give me same error. I believe the issue is actually within the Make module itself. After contacting support, I was told it was a limitation of the Facebook API, and nothing was done. Even if it were a Meta limitation, the Make module used to work fine and suddenly stopped working. That’s why I think that, for this module to continue to exist, Make itself should verify and fix this issue.

In my specific case, my solution was to remove the module and create my own application inside Facebook using the Meta API, with a webhook connected to Cloudflare and then to Make. In my case, it actually turned out to be better, because it’s faster and uses fewer credits.

1 Like

It’s great to hear that you found a workaround. Congratulations! :clap:t2:

Maybe you can share details here for future reference?

1 Like

Seem to be expericing this exact same issue. Everything has was working fine for well over a year, and then suddenly started getting this error around Feb 27th - 28th. This is whilst limit always having been set at 1, and start date 24 - 48 hours.

Exactly the same thing happen for me on the same day. The same modul for other pages works just fine. It’s only for one specific page that I’m experiencing this issue…