Google Ads API (Python, v6): New Error: "Enum ChangeEventResourceType has no name defined for value 13"

90 views
Skip to first unread message

Mat

unread,
Feb 11, 2021, 9:05:36 AM2/11/21
to AdWords API and Google Ads API Forum
Hi,

a Python script that has been running for several weeks now without errors keeps throwing a new Error since tonight:

"Error: Enum ChangeEventResourceType has no name defined for value 13"

when calling this query to the SearchStream Service (customer id doesn't matter):

query: "SELECT change_event.ad_group,change_event.campaign, change_event.change_date_time, change_event.change_resource_type, change_event.changed_fields, change_event.client_type, change_event.resource_change_operation, change_event.user_email, change_event.resource_name FROM change_event WHERE change_event.change_date_time >= \"2021-01-18\"       AND change_event.change_date_time < \"2021-01-19\" ORDER BY change_event.change_date_time LIMIT 10000"


Please have a look into this issue and make sure to keep backwards compatibility in this "non breaking" update. 

Regards
Mat

Google Ads API Forum Advisor Prod

unread,
Feb 11, 2021, 4:06:11 PM2/11/21
to m...@keyword-experte.de, adwor...@googlegroups.com
Hi Mat,

Thanks for reaching out. Can you please reply privately and provide the request and response logs associated with this SearchStream request? If you do not have logging configured, please see this guide for configuring logging for the Python client library.

Thanks,
Matt
Google Ads API Team

Google Logo
Matt
Google Ads API Team
 


ref:_00D1U1174p._5004Q2CQ1QQ:ref

Mat

unread,
Feb 12, 2021, 2:03:10 AM2/12/21
to AdWords API and Google Ads API Forum
Hi Matt,

the "reply privately" button is greyed out. 

But anyhow:
The issue seems to be that the "ChangeEventResourceType" v6 now (after the 6.1 update) contains 14 enums, while the current v6 version of the /google/ads/google_ads/v6/proto/enums/change_event_resource_type_pb2.py only addresses 9 of them:

 values=[
    _descriptor.EnumValueDescriptor(
      name='UNSPECIFIED', index=0, number=0,
      serialized_options=None,
      type=None,
      create_key=_descriptor._internal_create_key),
    _descriptor.EnumValueDescriptor(
      name='UNKNOWN', index=1, number=1,
      serialized_options=None,
      type=None,
      create_key=_descriptor._internal_create_key),
    _descriptor.EnumValueDescriptor(
      name='AD', index=2, number=2,
      serialized_options=None,
      type=None,
      create_key=_descriptor._internal_create_key),
    _descriptor.EnumValueDescriptor(
      name='AD_GROUP', index=3, number=3,
      serialized_options=None,
      type=None,
      create_key=_descriptor._internal_create_key),
    _descriptor.EnumValueDescriptor(
      name='AD_GROUP_CRITERION', index=4, number=4,
      serialized_options=None,
      type=None,
      create_key=_descriptor._internal_create_key),
    _descriptor.EnumValueDescriptor(
      name='CAMPAIGN', index=5, number=5,
      serialized_options=None,
      type=None,
      create_key=_descriptor._internal_create_key),
    _descriptor.EnumValueDescriptor(
      name='CAMPAIGN_BUDGET', index=6, number=6,
      serialized_options=None,
      type=None,
      create_key=_descriptor._internal_create_key),
    _descriptor.EnumValueDescriptor(
      name='AD_GROUP_BID_MODIFIER', index=7, number=7,
      serialized_options=None,
      type=None,
      create_key=_descriptor._internal_create_key),
    _descriptor.EnumValueDescriptor(
      name='CAMPAIGN_CRITERION', index=8, number=8,
      serialized_options=None,
      type=None,
      create_key=_descriptor._internal_create_key),
  ],

So - will this problem be fixed with the library updates next week?
But even if: I don't think, that it's a good idea of you to break code backwards in a minor version.

Regards
Mat

Google Ads API Forum Advisor Prod

unread,
Feb 15, 2021, 1:48:10 AM2/15/21
to m...@keyword-experte.de, adwor...@googlegroups.com
Hi Mat,

I work with Matt and allow me to assist you for now.

The request and response logs should look similar to their respective links. If you haven't yet, logging can be enabled by referring to this guide for Python.

Once enabled, you may retry your request and send to us the generated logs. Since you are unable to use the Reply privately to author option, you may send the details to our (googleadsa...@google.com) alias instead.

Best regards,

Google Logo
Peter Laurence Napa Oliquino
Google Ads API Team
 


ref:_00D1U1174p._5004Q2CQ1QQ:ref
Reply all
Reply to author
Forward
0 new messages