Error with Facebook Ads to BigQuery connection

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

Error message indicates credentials do not have enough permissions. Suggested actions include checking Ad Account Id, re-authenticating if using FB oauth, or refreshing access token with required permissions.


Question

Hi everyone, I have a facebook ads to bigquery connection running for months now but last night we started getting the following error for some reason. Anyone knows what the issue might be? Any help is appreciate it!
Failure reason: Credentials don't have enough permissions. Check if correct Ad Account Id is used (as in Ads Manager), re-authenticate if FB oauth is used or refresh access token with all required permissions


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["facebook-ads", "bigquery-connection", "credentials-permissions", "ad-account-id", "oauth", "access-token"]
2

Maybe we should create a Github issue for airbyte connector?

3

don’t know if it’s an airbyte issue

4

i have error 100 and subcode 33

5

We are facing the same issue.
II have tried to recreate the access token and I have noticed that the premission ‘business_management’ is not displayed.

Could this be the reason?

6

we are facing the issue as well since saturday
We tried to update the token too but didnt work…
On our side we have the business_management permission

7

for the ads_read permission, I have status Inactive and Verification required. Do you have this too?

8

https://developers.facebook.com/support/bugs/383587584813197/

9

Same here, it seems to be fixed

10

Same here, seems it’s already fixed

11

now it seems it’s working again

12

<@U05DEJAUL77> did you change anything to make it work?

13

I can confirm that, too!

14

Hi again guys, any idea how this is fixed? And did all API consumers had this issue or any particular group? I am trying to understand if this was Airbyte related issue or Meta related.

15

I still think the connector should get an update to prevent this next time

16

Hey guys, any progress? I am still waiting for a fix from airbyte/meta

17

I see that Airbyte connector is using the Meta API version v19.0, do you guys think it would help if we bump it up to one of the newer versions?

18

the latest version uses v21, but still same error, I already tried it

19

Unfortunately, we have not yet found a solution. We have written to our current contact at Meta and are now waiting for an answer.

I will let you know when there is an update from our side.

20

<@U06RSTU4L03> have you found something? i’m still on it, but nothing