Facebook and Bing Errors

1,169 views
Skip to first unread message

Yaniv Greizas

unread,
Jun 29, 2016, 7:12:54 AM6/29/16
to Supermetrics
Hi, 

I have a file with many queries that is being refreshed everyday.
From some reason, all of The Facebook queries as well as all of Bing's are with error today. 

Facebook: Error: Error validating access token: The user is enrolled in a blocking, logged-in checkpoint - although I am logged in. 

BingError: ERROR 2010 InvalidCustomDateRangeEnd The specified report time contains an invalid custom date range end. Please submit a report request with valid start and end dates for the custom date range.
The dates are Jun 1-30 - I know it's in the future, but I always use it like it and it was fine until today. 


Mikael Thuneberg

unread,
Jun 29, 2016, 7:54:43 AM6/29/16
to automate...@googlegroups.com
FB: See https://stackoverflow.com/questions/36401621/facebook-oauthexception-code-190-subcode-490-user-is-enrolled-in-a-blocking-l, there's some problem in your FB account that you need to resolve.

Bing: We made a change that should prevent this from happening in the future.

--
You received this message because you are subscribed to the Google Groups "Supermetrics" group.
To unsubscribe from this group and stop receiving emails from it, send an email to automateanalyt...@googlegroups.com.
Visit this group at https://groups.google.com/group/automateanalytics.
To view this discussion on the web visit https://groups.google.com/d/msgid/automateanalytics/89a6779a-a4d4-4bb9-b055-003726059d7d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Yaniv Greizas

unread,
Jun 29, 2016, 8:20:13 AM6/29/16
to Supermetrics
I did have an issue on FB, as described on stackoverflow, and was logged out from FB.
However. I logged in again, to my FB as well as in to my Business Manger, all looks fine but supermetrics still get this error message. 

How can I solve this? 

Mikael Thuneberg

unread,
Jun 29, 2016, 8:30:54 AM6/29/16
to automate...@googlegroups.com
I don't know, that error is coming from FB, not our system. Maybe there's some delay for getting the FB API back running.

Reply all
Reply to author
Forward
0 new messages