1. Home
  2. Docs
  3. Handling Errors
  4. Facebook Ads Error List

Facebook Ads Error List

Here you can find list of all the errors for the Facebook ads data source in DigiXport.

The error will be displayed in the message box at the bottom of the addon, when you click on Export button.

You can mail us if the error you got is not mentioned in the list.

#1 Reason: Please reduce the amount of data you’re asking for, then retry your request

The error mentioned is due to the FB server taking long time to respond due to large amount of data requested.

Solution:

You can try to reduce the amount of data you’re requesting by

  1. Importing data for shorter date range. You can import the data in chunks and append it the older data.
  2. Try to use less breakdown fields such as Age, Gender, Time of day in a single query.
  3. When you use ad level metrics such as ad name, ad id, etc it might give an error if the data is too large.  

 

#2 Reason: (#100) For field ‘insights’: since must be less than or equal to until in time_range

The error occurs when the start date is greater than the end date in the selected date range.

Solution:

The error mostly occurs if you’re using custom date range from the sheet cell. 

You can check if the start date is less than or equal to the end date range. Once fixed you can rerun the query.

 

# 3 Reason: Error validating access token: Sessions for the user are not allowed because the user is not a confirmed user.

The error occurs when the session for the use has been expired.

Solution:

You can re-authorize the Facebook ads datasource with the correct authorization email.

 

# 4 Reason: (#100) Missing permissions

The error occurs when you don’t have permission to access the particular ad account or the token has expired.

Solution:

You can re-authorize the Facebook ads datasource and re-run the query.

 

#5 Reason: An unknown error occurred

You can refer to the #1 error mentioned on this page.

 

# 6 Service invoked too many times in a short time.

The error is not related to facebook server. It happens when many queries are run in short amount of time.

Solution:

You can wait for some time and then re-try running the query.

 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *