I have the same problem … 

 

Error turning Zap on: (#100) Object does not exist, cannot be loaded due to missing permission or reviewable feature, or does not support this operation. This endpoint requires the 'pages_read_engagement' permission or the 'Page Public Content Access' feature or the 'Page Public Metadata Access' feature.. Refer to https://developers.facebook.com/docs/apps/review/login-permissions#manage-pages, https://developers.facebook.com/docs/apps/review/feature#reference-PAGES_ACCESS and https://developers.facebook.com/docs/apps/review/feature#page-public-metadata-accessfor details.

please send me update to my email cpe4ever@gmail.com

We are having this same exact error as well. Please resolve as quickly as possible!

I have the same error. Help

Oh no, @Pierre-Hugo! I’m so sorry to hear that!

This is still marked as closed but if you’re running into this still I might recommend contacting our friends in support to dig into this a bit more with you.

Has this been revolved? Because I’m still getting the error.

Hey @Hakim, hope you’re well!

I’ve just added you to the report and we’ll be sure to notify you as soon as the issue is resolved.

Also affected!!

Same error here. Please add me to the list.

Thanks!

FYI, we contacted Facebook and they confirmed that it’s problem on Zapier side. Please fix it asap because we don’t have capacity to contact all our Facebook leads manually, thus we are losing them.

Please check a screenshot attached:

Hello @nicksimard,

I am also experiencing the same issue and getting a #100 error. Is it be possible to be notified when the issue has been resolved? 

Hi @JallaJ - You’ve been added to the report and will be contacted directly via email. Thanks!

Hi, I have the same issue. 

Could you also add me to the email list? 

Thanks!

Hello! 

I think I have the same problem in my account :

Error turning Zap on: (#100) Object does not exist, cannot be loaded due to missing permission or reviewable feature, or does not support this operation. This endpoint requires the 'pages_read_engagement' permission or the 'Page Public Content Access' feature or the 'Page Public Metadata Access' feature.. Refer to https://developers.facebook.com/docs/apps/review/login-permissions#manage-pages, https://developers.facebook.com/docs/apps/review/feature#reference-PAGES_ACCESS and https://developers.facebook.com/docs/apps/review/feature#page-public-metadata-accessfor details.

Is it possible to be notified when the problem is resolved? 

My company and I will not subscribe to the premium version if it’s not working.

Thanks.

Regards

please add me to the list as well!

same problem. add me to the list please!

Hi, thanks for sharing this info.

I am also experiencing the same issue, appreciate there isn’t a fix yet, if I could also be added to the email list that would be helpful, thanks.

Hi @GGP

I’ve added you to the list of affected users as well, thanks!

Hey @warstm, hope you’re doing well!

I just added you to the report, we’ll be sure to alert you as soon as the issue is resolved. :)

add me to the list please and any updates yet

Same issue here. Please email me when it is fixed

Hi @john712!

The error you’re seeing is actually a bug with the Facebook Messenger app integration. From the error message, we can derive there is an issue with permission or scope setting, which prevents anyone to turn on their Zap when using that trigger.

Reviewing this, I can see that other users have run into this issue as well, so I'm adding your email to the list of affected users, so that if and once this has been resolved, you'll be the first to know.

Sadly, there is no workaround I can provide here, because this is something that needs to be updated in the backend, and while we don't have a timeline on when this will be fixed, we'll be sure to reach out per email once a resolution has been found.

@Yacine and @spacewaffle Thanks for your messages, I’ve added you to the issue report, which means that you’ll get an email when we have an update. 

Same issue… add me as well pls.

Can I be adde to this as well?

I see this same issue with users from 9 months ago… that thread was closed with Zaper stating they were “looking into the issue”.  Guess I need to cancel my subscription.