This page lists common errors and provides tips on preventing and handling them. For further support, visit our forum. We've grouped the errors into these categories:
- Entities
- Errors related to AdWords API entities such as campaigns, ads, or ad groups.
- Authentication/Authorization
- OAuth and general authentication/authorization errors.
- Miscellaneous
- General errors such as exceeding limits or missing specifications.
Categories
Entities
Accounts
-
NotWhitelistedError.CUSTOMER_ADS_API_REJECT
-
OperationAccessDenied.ADD_OPERATION_NOT_PERMITTED
-
OperationAccessDenied.MUTATE_ACTION_NOT_PERMITTED_FOR_CLIENT
-
QuotaCheckError.ACCOUNT_DELINQUENT
-
QuotaCheckError.ACCOUNT_INACCESSIBLE
-
QuotaCheckError.TERMS_AND_CONDITIONS_NOT_SIGNED
-
QuotaCheckError.DEVELOPER_TOKEN_NOT_APPROVED
-
QuotaCheckError.INCOMPLETE_SIGNUP
-
QuotaCheckError.INVALID_TOKEN_HEADER
-
QuotaCheckError.MONTHLY_BUDGET_REACHED
Campaigns
Ad groups
Ads
-
AdError.CANNOT_USE_AD_SUBCLASS_FOR_OPERATOR
-
AdError.INVALID_INPUT
-
AdError.LINE_TOO_WIDE
-
AdGroupAdError.AD_GROUP_AD_LABEL_ALREADY_EXISTS
-
AdGroupAdError.CANNOT_OPERATE_ON_DELETED_ADGROUPAD
-
AdPolicyError
Budget orders
Budgets
-
BudgetError.MONEY_AMOUNT_LESS_THAN_CURRENCY_MINIMUM_CPC
-
BudgetError.NON_MULTIPLE_OF_MINIMUM_CURRENCY_UNIT
Bids
-
BiddingErrors.BID_TOO_HIGH_FOR_DAILY_BUDGET
-
BiddingErrors.BID_TOO_MANY_FRACTIONAL_DIGITS
-
BiddingErrors.BID_TOO_BIG
Criteria
-
AdGroupCriterionError.INVALID_KEYWORD_TEXT
-
CriterionError.AD_SCHEDULE_EXCEEDED_INTERVALS_PER_DAY_LIMIT
-
CriterionError.KEYWORD_HAS_INVALID_CHARS
-
PolicyViolationError
-
CriterionPolicyError
Feeds and extensions
-
CampaignFeedError.FEED_ALREADY_EXISTS_FOR_PLACEHOLDER_TYPE
-
CampaignFeedError.CANNOT_ADD_ALREADY_EXISTING_CAMPAIGN_FEED
-
FeedItemError.CANNOT_OPERATE_ON_DELETED_FEED_ITEM
Conversions
-
ConversionTrackingError.DUPLICATE_NAME
-
OfflineConversionError.EXPIRED_CLICK
-
OfflineConversionError.INVALID_CONVERSION_TYPE
-
OfflineConversionError.TOO_RECENT_CLICK
-
OfflineConversionError.UNAUTHORIZED_USER
Reports
-
AuthenticationError.CLIENT_CUSTOMER_ID_INVALID
-
QueryError.INVALID_WHERE_CLAUSE
-
QueryError.PARSING_FAILED
-
ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH
-
ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT
-
ReportInfoError.INVALID_USER_ID_IN_HEADER
-
RequestError.INVALID_INPUT
Authentication/Authorization
Authentication
-
AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED
-
AuthenticationError.CUSTOMER_NOT_FOUND
-
AuthenticationError.GOOGLE_ACCOUNT_COOKIE_INVALID
-
AuthenticationError.NOT_ADS_USER
-
AuthenticationError.OAUTH_TOKEN_INVALID
Authorization
Miscellaneous
Redundancy
Missing/invalid specifications
-
EntityNotFound.INVALID_ID
-
NotEmptyError.EMPTY_LIST
-
RangeError.TOO_LOW
-
RequiredError.REQUIRED
-
SelectorError.INVALID_FIELD_NAME
-
SelectorError.INVALID_PREDICATE_VALUE
-
SelectorError.MISSING_PREDICATE_VALUES
Limit exceeded
-
CustomerSyncError.TOO_MANY_CHANGES
-
QuotaCheckError.QUOTA_EXCEEDED
-
RateExceededError.RATE_EXCEEDED
-
SizeLimitError.RESPONSE_SIZE_LIMIT_EXCEEDED
Unallowed actions
Others
Errors
CANNOT_USE_AD_SUBCLASS_FOR_OPERATOR |
|
---|---|
Summary | This operator cannot be used with a subclass of Ad. |
Common causes | You've tried to modify attributes other than status of the ad. |
Recommended handling tips | N/A |
Prevention tips | Once an ad is created, it cannot be modified. If you would like
to modify the ad, you must make a new ad and then remove the old one.
The status of the ad is, however, modifiable via
AdGroupAdService.mutate(). | INVALID_INPUT |
Summary | One of the fields in an ad contains invalid characters. |
Common causes | Using special characters in URLs |
Recommended handling tips | N/A |
Prevention tips | Validate URLs in your application before making a request to the API. | LINE_TOO_WIDE |
Summary | One of the lines in an ad was longer than the maximum allowed length. The length limits are documented in the Google Ads help center. |
Common causes |
|
Recommended handling tips | N/A |
Prevention tips | Validate the length of the line before making the request. |
AD_GROUP_AD_LABEL_ALREADY_EXISTS |
|
---|---|
Summary | This label is already associated with some of these ads. |
Common causes | You’ve tried to associate the label with ads that already have them associated. |
Recommended handling tips | N/A |
Prevention tips | Check first to see if the label to be added is already associated with the ads using AD_PERFORMANCE_REPORT. You can get the IDs and names of labels associated with the ads by this report. | CANNOT_OPERATE_ON_DELETED_ADGROUPAD |
Summary | An operation attempted to update a removed ad. |
Common causes | Once an ad is removed, it can no longer be updated (including changes to its status). |
Recommended handling tips | N/A |
Prevention tips | Ensure that your code does not attempt to update removed ads. |
INVALID_KEYWORD_TEXT |
|
---|---|
Summary | The keyword text contains invalid characters. A list of valid characters is available on the Google Ads help center. |
Common causes | The keyword text contains invalid characters. |
Recommended handling tips | N/A |
Prevention tips |
|
DUPLICATE_ADGROUP_NAME |
|
---|---|
Summary | An ad group is being added or renamed, but the name is already being used by another ad group. |
Common causes | Creating a new ad group with the name of an existing active or paused ad group |
Recommended handling tips | Log the error and/or present an error message to the user, optionally suggesting a unique ad group name or showing the list of names in use. |
Prevention tips | N/A |
CLIENT_CUSTOMER_ID_INVALID |
|
---|---|
Summary | Client customer ID is not a number. |
Common causes | You've specified your client customer ID wrongly. |
Recommended handling tips | N/A |
Prevention tips | Client customer ID is always composed of digits with no alphabets or other punctuations except "-", and is in the form 123-456-7890. See this page for details. | CLIENT_CUSTOMER_ID_IS_REQUIRED |
Summary | Client customer ID was not specified in the HTTP header. |
Common causes | You've not specified your client customer ID in the HTTP header. |
Recommended handling tips | N/A |
Prevention tips | Client customer ID is required for all cases except for when using CustomerService.get(). Therefore, make sure you've specified it in the HTTP header. Consider using our client libraries, as they handle this for you. | CUSTOMER_NOT_FOUND |
Summary | No account found for the customer ID provided in the header. |
Common causes | Trying to access an account that was just created with
ManagedCustomerService before the account is established in the backend. |
Recommended handling tips | Wait an initial five minutes, then retry every 30 seconds. |
Prevention tips | Wait a few minutes after the account is created before issuing requests against it. | GOOGLE_ACCOUNT_COOKIE_INVALID |
Summary | The access token in the request header is either invalid or has expired. |
Common causes |
|
Recommended handling tips | Request a new token following these guidelines. If you're using one of our client libraries, consult its documentation on how to refresh the token. |
Prevention tips | Store and reuse access tokens until they expire. | NOT_ADS_USER |
Summary | The login used to generate the access token is not associated with any Google Ads account. |
Common causes | The login information provided corresponds to a Google account that does not have AdWords API enabled. |
Recommended handling tips | Make sure to log in with a valid Google Ads account (typically your manager account) for the OAuth flow. |
Prevention tips | N/A | OAUTH_TOKEN_INVALID |
Summary | OAuth access token in the header is not valid. |
Common causes | Your access token passed with the HTTP header was not correct. |
Recommended handling tips | N/A |
Prevention tips | Make sure you've passed the correct access token associated with your account. It's sometimes confused with refresh tokens and authorization codes. If you would like to get a credential that can access all client accounts under a manager account, make sure you get the refresh token for the manager account. Review our guide for details about access token and refresh token. For more detail, see OAuth2 Authentication guide. |
UNABLE_TO_AUTHORIZE |
|
---|---|
Summary | There was an issue with completing authorization for a given user/account. |
Common causes | Attempting to create an account via ManagedCustomerService.mutate under a non-manager account. |
Recommended handling tips | N/A |
Prevention tips |
Use ManagedCustomerService to determine if the account is a
manager account. The field
ManagedCustomer.canManageClients
should be true .
|
USER_PERMISSION_DENIED |
Summary | There is no link between the manager account authenticated in the request and the client account specified in the headers. |
Common causes |
|
Recommended handling tips | N/A |
Prevention tips | Use ManagedCustomerService to determine which
client accounts are linked to your manager account. |
BID_TOO_HIGH_FOR_DAILY_BUDGET |
|
---|---|
Summary | The bid on a keyword or ad group is higher than the daily budget of the campaign. |
Common causes | N/A |
Recommended handling tips | N/A |
Prevention tips | Use CampaignService to get the
budget
of the campaign, then validate ad group or keyword bids against the budget
before performing the request. |
BID_TOO_MANY_FRACTIONAL_DIGITS |
Summary | The bid value is not an exact multiple of the minimum unit of the account's
currency. For example, US$0.015 (15000 in micros) is not a valid bid. |
Common causes | N/A |
Recommended handling tips | N/A |
Prevention tips | Verify that bids are multiples of the minimum unit for the account's currency. | BID_TOO_BIG |
Summary | The error is returned even though the bid is within the campaign budget. |
Common causes | N/A |
Recommended handling tips | N/A |
Prevention tips | Check if the account is participating in Google Ad Grants. If so, restrict CPC bids to the maximum prescribed by the program. |
GENERIC_BILLING_ERROR |
|
---|---|
Summary | An attempt to mutate BudgetOrder failed because of generic billing errors. |
Common causes |
|
Recommended handling tips | N/A |
Prevention tips |
|
MONEY_AMOUNT_LESS_THAN_CURRENCY_MINIMUM_CPC |
|
---|---|
Summary | The budget amount is too small. |
Common causes | N/A |
Recommended handling tips | N/A |
Prevention tips | Verify that budget amount is greater than or equal to the minimum unit for the account's currency. | NON_MULTIPLE_OF_MINIMUM_CURRENCY_UNIT |
Summary | The budget amount will have too many significant decimal places when converted from a micro amount to an amount in the account's currency. |
Common causes | N/A |
Recommended handling tips | N/A |
Prevention tips | Verify that budget amount is divisible by the minimum unit for the account's currency. |
DUPLICATE_CAMPAIGN_NAME |
|
---|---|
Summary | A campaign is being added or renamed, but the name is already being used by another campaign. |
Common causes | Creating a new campaign with the name of an existing active or paused campaign. |
Recommended handling tips | Log the error and/or present an error message to the user, optionally suggesting a unique campaign name or showing the list of names in use. |
Prevention tips | N/A |
CANNOT_ADD_ALREADY_EXISTING_CAMPAIGN_FEED |
|
---|---|
Summary | Campaign feed already exists and thus the new feed cannot be added. |
Common causes | You tried to add a new campaign feed via ADD operation although there already exists one. |
Recommended handling tips | N/A |
Prevention tips | Check if a campaign feed exists using PLACEHOLDER_REPORT before adding.
If you want to modify the existing campaign feed, use the SET operator. | FEED_ALREADY_EXISTS_FOR_PLACEHOLDER_TYPE |
Summary | A campaign already has an active feed for the placeholder type. |
Common causes | You tried to add a feed for a certain placeholder type for a campaign that already has active feed for the placeholder type. |
Recommended handling tips | N/A |
Prevention tips | Check if your campaign has active feed for the particular placeholder type before adding. Use PLACEHOLDER_REPORT to check if there exists any feed for the particular placeholder type. |
DUPLICATE_NAME |
|
---|---|
Summary | Found two conversion types with the same name. |
Common causes | You've specified two identical names when attempting to create or rename multiple conversion types. |
Recommended handling tips | N/A |
Prevention tips | Check the conversion name before adding. Use ConversionTrackerService.get() to get the list of available conversions. See Selector Fields for all selectable fields for this service. |
AD_SCHEDULE_EXCEEDED_INTERVALS_PER_DAY_LIMIT |
|
---|---|
Summary | The number of AdSchedule entries in a day exceeds the limit. |
Common causes | Creating more than the limit of six intervals in a day. |
Recommended handling tips | N/A |
Prevention tips | For a given AdSchedule, create no more than six intervals in a day. | KEYWORD_HAS_INVALID_CHARS |
Summary | Adding / editing keywords that contain invalid characters. |
Common causes | Use special characters like ! @ % * in the keywords. |
Recommended handling tips | N/A |
Prevention tips | Make sure you don’t use any unallowed characters in the keywords. See this link for more information. |
TOO_MANY_CHANGES |
|
---|---|
Summary | There were too many changed entities to return. |
Common causes | Specifying too broad of a date range |
Recommended handling tips | Narrow the date range and retry the request. If the error persists, assume everything has
changed and use each campaign data services' get requests to retrieve the most recent campaign data. |
Prevention tips | N/A |
CONCURRENT_MODIFICATION |
|
---|---|
Summary | Multiple processes are trying to update the same entity at the same time. |
Common causes |
|
Recommended handling tips | Wait for about 30 seconds, then retry the request. |
Prevention tips |
|
DUPLICATE_ELEMENT |
|
---|---|
Summary | The request contains two parameters that are identical and redundant. |
Common causes | N/A |
Recommended handling tips | N/A |
Prevention tips | Remove duplicates (operations, parameters, list elements) before making the request. Look for fields that have the DistinctElements constraint. |
INVALID_ID |
|
---|---|
Summary | The ID of the entity you are operating on isn't valid. |
Common causes |
|
Recommended handling tips |
Log the error and examine the trigger
field to ensure that the ID is being specified correctly and belongs to the
current account.
|
Prevention tips | N/A |
CANNOT_OPERATE_ON_DELETED_FEED_ITEM |
|
---|---|
Summary | An operation attempted to update a removed feed item. |
Common causes | Once a feed item is removed, it can no longer be updated (including changes to its status), but you've tried to do so. |
Recommended handling tips | N/A |
Prevention tips | Ensure that your code does not attempt to update removed feed items. |
UNEXPECTED_INTERNAL_API_ERROR |
|
---|---|
Summary | Something unexpected happened while processing the request. |
Common causes |
|
Recommended handling tips | Wait for about 30 seconds, then retry the request. If this error occurs frequently, post the details to the forum for further troubleshooting. |
Prevention tips | N/A |
EMPTY_LIST |
|
---|---|
Summary | A required list is empty. |
Common causes | Passing in an empty list of operations to a mutate method |
Recommended handling tips | N/A |
Prevention tips | N/A |
CUSTOMER_ADS_API_REJECT |
|
---|---|
Summary | The account is temporarily in read-only mode. |
Common causes | The Google Ads system is performing a backend migration on the account. |
Recommended handling tips | Wait for about 30 minutes, then retry the request. |
Prevention tips | N/A |
EXPIRED_CLICK |
|
---|---|
Summary | Click is too old for its conversion to be imported. |
Common causes | This click is either too old to be imported or occurred before the conversion window for the specified combination of conversion date and conversion name (default is 90 days). |
Recommended handling tips | N/A |
Prevention tips | Ensure that your clicks to be uploaded occurred during these 90 days and not too old. | INVALID_CONVERSION_TYPE |
Summary | Cannot find conversion name in the account. |
Common causes |
|
Recommended handling tips | N/A |
Prevention tips | Ensure that you use the right conversion name by looking it up first using ConversionTrackerService.get(). If you change the effective conversion account to the manager account (see cross-account conversion tracking), then your uploads for that account will start working only for conversions where the click date is after you make that change. See this section for more tips and rules about uploading conversions. | TOO_RECENT_CLICK |
Summary | Click is not yet in the system. |
Common causes | This click occurred less than 24 hours ago, so it's too recent to be uploaded. |
Recommended handling tips | Try again after a day or so. |
Prevention tips | Ensure to upload clicks that occurred more than 24 hours ago. | UNAUTHORIZED_USER |
Summary | Not authorized to manage this click. |
Common causes | You've tried to upload conversions for a different customer that your account does not manage. |
Recommended handling tips | N/A |
Prevention tips | Ensure that your uploaded clicks really belong to the account of your credential used to make SOAP calls. |
ADD_OPERATION_NOT_PERMITTED |
|
---|---|
Summary | The ADD operator can't be used for operations in the service and target account. |
Common causes | Attempting to add a campaign to a manager account. |
Recommended handling tips | N/A |
Prevention tips | When authenticating as a manager account, ensure that the clientCustomerId header refers to a Google Ads account. | MUTATE_ACTION_NOT_PERMITTED_FOR_CLIENT |
Summary | The attempted operation cannot be performed through the API. |
Common causes | Attempting to modify a campaign that was created using the AdWords Express. |
Recommended handling tips | Flag the campaign in your system as being read-only. |
Prevention tips | N/A | OPERATION_NOT_PERMITTED_FOR_REMOVED_ENTITY |
Summary | The operation is not permitted for the removed entity. |
Common causes | You've tried to update the entity, e.g., campaign, that was already removed. |
Recommended handling tips | N/A |
Prevention tips | Always keep tracks of the statuses of your entities and confirm their statuses before making changes. Statuses of entities can usually be fetched using the report field Status. |
Summary | An ad or keyword you are adding violates a Google Ads policy. |
Common causes | Your ad or keyword contains trademarks or medical terms. |
Recommended handling tips | If the returned
isExemptable
field is true, then you can request an exemption for your ad or keyword. To
request an exemption:
|
Prevention tips | Use the
validateOnly header to
check ads and keywords for errors before attempting to add them.
|
INVALID_WHERE_CLAUSE |
|
---|---|
Summary | The WHERE clause could not be parsed. |
Common causes | The WHERE clause of query doesn't comply with the AWQL grammar. |
Recommended handling tips | N/A |
Prevention tips | Ensure that your query is correct based on the AWQL grammar. See this guide for details. | PARSING_FAILED |
Summary | Errors when trying to parse a query that doesn't match the AWQL grammar. |
Common causes | You've made mistakes in your AWQL query. |
Recommended handling tips | N/A |
Prevention tips | Ensure that your query is correct based on the AWQL grammar. See this guide for details. |
ACCOUNT_DELINQUENT |
|
---|---|
Summary | The manager account that was used to register for API access does not have an active billing mechanism. |
Common causes | The credit card used to pay for API charges has expired. An account must have an active billing mechanism at all times. |
Recommended handling tips | Update the billing information in your account. |
Prevention tips | N/A | ACCOUNT_INACCESSIBLE |
Summary | The target account has been temporarily disabled due to suspicious activity and cannot be accessed via the API. |
Common causes | N/A |
Recommended handling tips | Contact your Google Ads account representative for more information. If you don't have a representative or don't know who they are, use the contact form in the Google Ads Help Center. |
Prevention tips | N/A | TERMS_AND_CONDITIONS_NOT_SIGNED |
Summary | You have not yet signed the Terms & Conditions. |
Common Causes | N/A |
Recommended handling tips |
Make sure that you've accepted the terms and conditions. If you're unable to do this, contact AdWords API Compliance and select the "I need to sign the AdWords API Terms & Conditions" option to obtain help. |
Prevention tips | Make sure that you complete the signup and accept the terms and conditions before trying to use the AdWords API. | DEVELOPER_TOKEN_NOT_APPROVED |
Summary | You are using an unapproved developer token to make calls against a production account. |
Common Causes | N/A |
Recommended handling tips |
An unapproved developer token can only make calls against test Google Ads accounts. See the test account guide for more information. You can make calls against a test account even before your developer token is approved, so you can get started on your application right away. If you think your token should have been approved, or it's taken more than 2 business days to get back to you, please first double-check your email to make sure you have not missed a communication from the API compliance team. If you still need help, you can contact the API compliance team for assistance in getting your token approved. |
Prevention tips | Make sure that your developer token is approved before using it in a production account. | INCOMPLETE_SIGNUP |
Summary | The developer token has not been approved and you're trying to use it for requests against a production account. |
Common causes | N/A |
Recommended handling tips |
An unapproved developer token can only make calls against test Google Ads accounts. See the test account guide for more information. You can make calls against a test account even before your developer token is approved, so you can get started on your application right away. If you think your token should have been approved, or it's taken more than 2 business days to get back to you, please first double-check your email to make sure you have not missed a communication from the API compliance team. If you still need help, you can contact the API compliance team for assistance in getting your token approved. |
Prevention tips | N/A | INVALID_TOKEN_HEADER |
Summary | The developer token in the request is missing or invalid. |
Common causes |
|
Recommended handling tips | N/A |
Prevention tips |
|
MONTHLY_BUDGET_REACHED |
Summary | The API monthly budget limit has been exceeded. |
Common causes | Exceeding your set budget for API usage. |
Recommended handling tips | N/A |
Prevention tips | Once you verify that there is no excessive usage due to a runaway program, increase the API monthly budget (via your manager account's My Account > API Center) to an appropriate amount. | QUOTA_EXCEEDED |
Summary | A system frequency limit has been exceeded. |
Common causes | Sending too many requests in a short period of time. |
Recommended handling tips | N/A |
Prevention tips | Set up short delays between requests or use BatchJobService to combine more operations in fewer requests. |
TOO_LOW |
|
---|---|
Summary | A value was lower than the minimum allowed. |
Common causes | Forgetting to specify an ID, which results in a value of 0 being passed in. |
Recommended handling tips | N/A |
Prevention tips | Note any range limitations documented in the API reference. |
RATE_EXCEEDED |
|
---|---|
Summary | Too many requests were made to the API in a short period of time. |
Common causes |
|
Recommended handling tips |
|
Prevention tips | Read the Rate Limits guide for in-depth information about this error. |
CUSTOMER_SERVING_TYPE_REPORT_MISMATCH |
|
---|---|
Summary | You are trying to run a report against a manager account. Reports can only be obtained for advertiser (non-manager) accounts. |
Common causes |
|
Recommended handling tips | N/A |
Prevention tips | Ensure that clientCustomerId in the reporting request corresponds to a non-manager account. The
ManagedCustomerService
can be used to get account information, and if
ManagedCustomer.canManageClients
is true then the account is a manager account.
|
INVALID_FIELD_NAME_FOR_REPORT |
Summary | Customer passed in invalid field name for a report type. |
Common causes | You've spelled some field names wrongly in your query. |
Recommended handling tips | N/A |
Prevention tips | Ensure that all specified field names are available for the report type you are using. Consult this page for all available report fields. |
INVALID_USER_ID_IN_HEADER |
|
---|---|
Summary | The client is using an invalid user or effective user ID in the header. |
Common causes |
|
Recommended handling tips | N/A |
Prevention tips |
|
INVALID_INPUT |
|
---|---|
Summary | The request is malformed. |
Common causes | Missing version string in the request URL to download reports. |
Recommended handling tips | N/A |
Prevention tips | Provide the version in the request URL. For example:
https://adwords.google.com/api/adwords/reportdownload/v201809 |
REQUIRED |
|
---|---|
Summary | The request is missing required information. |
Common causes |
|
Recommended handling tips | Log the error and/or present an error message to the user. The
fieldPath attribute of the error indicates which field is
missing. |
Prevention tips | Read the API reference to find out which fields are required. |
INVALID_FIELD_NAME |
|
---|---|
Summary | The field name was incorrect or does not exist in the service. |
Common causes | You've specified a wrong field name or misspelled it. |
Recommended handling tips | N/A |
Prevention tips | Ensure you've specified correct field names for the service you're using. Check Selector Fields for all selectable fields for a given service. | INVALID_PREDICATE_VALUE |
Summary | The predicate value was not valid. |
Common causes | You've specified a wrong predicate value, such as using a string as a predicate for a field that is of integer type. |
Recommended handling tips | N/A |
Prevention tips | Ensure you've specified correct values for the field used as predicate. Validate fields for a given service with the reference docs (for example, CampaignService). | MISSING_PREDICATE_VALUES |
Summary | The predicate values were empty. |
Common causes | You've specified to use predicates, but some of their values were not provided. |
Recommended handling tips | N/A |
Prevention tips | Ensure to provide values when specifying predicates in the selector. |
RESPONSE_SIZE_LIMIT_EXCEEDED |
|
---|---|
Summary | The response contains too many items. |
Common causes | When making a get call (e.g.
AdGroupCriterionService.get() ) the number of returned items
may exceed the response size limit (150K). |
Recommended handling tips | N/A |
Prevention tips |
|