** RESOLVED ** Issue with Facebook Insights - "FB error: (#190) This method must be called with a Page Access Token" - 02/04/2020

** UPDATE 01/09/2020 18:15 EEST **

After thorough investigations and adjustments we are now confident that this error should be fixed. 

If you still see any errors, it can mean you’re running a query that includes a page which you no longer have access to. In order to fix this problem, you most likely need to re-authenticate the data source with these instructions.

We are terribly sorry about any inconvenience caused by this problem. If you still see any issue with your query, please don’t hesitate to reach out to our support

** UPDATE 26/06/2020 12:20 EEST ** 

We have tried pretty much every option we know of to try to workaround or remove the Facebook #190 error, but sadly, nothing so far has helped. This seems to show that the issue is on the Facebook side and we need Facebook’s engineering team to resolve this.

If you have an account manager at Facebook, please contact them about this issue and provide the bug link https://developers.facebook.com/support/bugs/3005014026186562/, so that hopefully they can communicate the impact of this issue to Facebook’s Engineering team. If you do not have an account manager, you can mark yourself as affected on the bug and follow it to get major updates as soon as they publish them.

We will update this article once we have any news to share. We apologize for the disruptions this has been causing and thank you for your patience.


We have been made aware of an issue with the Facebook Marketing API that can lead to this error in Supermetrics Queries for Facebook Insights:

  • "FB error: (#190) This method must be called with a Page Access Token. Please log out of the Facebook via the sidebar and then log in again."

In some cases queries might fail in one refresh and then work on the next.

We are fairly certain that this issue is on Facebook's side because of the intermittent nature of the failure. There is an open bug report on Facebook's side: https://developers.facebook.com/support/bugs/3005014026186562/

To raise the priority, we kindly ask you to vote this Facebook bug report by clicking “Same here!” button with flag icon. We'll update this article as soon as we have more information about the problem. 

Our apologies for any inconvenience caused by this.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.