Calls failing to "change_event" report

[kol...@exito.de]

Hey Googlers,

calls to the "change_event" report of the Ads API (v6) always fail when any of these three fields is included in the API query ...

change_event.old_resource

change_event.new_resource

change_event.changed_fields

... and the changes made in the Ads account include changes to the second headline of expanded text ads.

Result:        "grpc_message":"Internal error encountered.","grpc_status":13

[Google Ads API Forum Advisor Prod]

Hi,

Thanks for posting your concern.

To investigate, could you provide the following details via Reply privately to author option?

• customer ID
• complete request and response logs
• request ID

Regards,

Ernie John Blanca Tacata Google Ads API Team

ref:_00D1U1174p._5004Q27uEVS:ref

[kol...@exito.de]

I'm not authorized to reply to the author although I'm logged in. Any suggestions to fix this?

[kol...@exito.de]

The problem seems to be restricted to the AD level, so if you filter it out then the API request works without problems (at least for our 200+ active accounts):

      WHERE change_event.change_resource_type NOT IN ('AD')

[Google Ads API Forum Advisor Prod]

Hi,

Thank you for providing further details about your issue.

To investigate the issue and the behavior that you've mentioned, please provide the requested details on this email address googleadsa...@google.com so that we can receive it privately.

[Mat]

Hi there,

I'm encountering a similar error while requesting a change_event report on an account where ads have been modified. I'll send a pm with the log to you.

Regards

Mat

[Google Ads API Forum Advisor Prod]

Hi Thomas,

Thanks for providing further details.

Allow me to discuss the issue to the rest of the team. We will revert back to you with updates about the issue.

[Google Ads API Forum Advisor Prod]

Hi Mat,

Could you provide the following details via Reply privately to author option to investigate?

• customer ID
• complete request and response logs
• request ID

If the Reply privately to author option is disabled on your end, please send it on this email address instead googleadsa...@google.com.

[Google Ads API Forum Advisor Prod]

Hi Mat,

I just found out that you already provided the necessary details on a separate thread.

Let me also discuss this information with rest of the team. Please keep an eye on this forum thread as we will provide updates here about the issue.

[Google Ads API Forum Advisor Prod]

Hi Mat,

Thanks for reporting this issue. We identified and fixed an issue at our end, and it should go live in the next server update. I'll update you once the fix is live.

Cheers
Anash

ref:_00D1U1174p._5004Q27uEVS:ref

[Mat]

Hi Anash,

great, thank you!

Regards

Mat

[duca...@gmail.com]

Hi there, 

Do we have any update? Looks like we started to see new failures from early this week due to similar errors. 

If our query include "NOT IN" as the condition, it will always fail with "invalid argument " error. For instance the following query will fail for sure. Do we have any details? Thanks!

SELECT label.id, label.status, label.name, label.text_label.background_color, label.text_label.description

FROM label

WHERE label.status NOT IN ('UNKNOWN')

ORDER BY label.id ASC

[duca...@gmail.com]

Hi team,

Do we have any update on this? We suspect this is an regression from Google Ads and would like to double confirm with you. 

[Google Ads API Forum Advisor Prod]

Hi Caihua,

We pushed a fix to our servers, so could you please confirm if the issue is addressed? If it persists, please respond with a fresh log and I'll follow up with the relevant teams again.

[duca...@gmail.com]

Thanks for the update. Unfortunately we still see this error from our side. I have replied privately with the request id for further investigation. 

Thanks!

[Mat]

Hi Anash,

I've now fetched the change_history of >200 client accounts for the last 30 days and did not run into an error. 

So I think it's safe to say that the error I reported on November, 11 has been fixed.

Thank you!

Regards

Mat

[duca...@gmail.com]

This is still happening from our side and I have provided request id privately about one month ago, there is no update yet. Can you pleas look into this? thank you!

[Caihua Du]

Adding the team alias here. Can you please help to check more of the request I provided earlier? Thank you’

On Wed, Dec 9, 2020 at 10:49 AM Caihua Du <duca...@gmail.com> wrote:

Thanks Anash. Unfortunately this issue still persists. I have pasted the latest debugging log from my side for your reference:

[2020-12-09 18:41:38Z] - Request made: Host: https://googleads.googleapis.com, Method: /google.ads.googleads.v6.services.GoogleAdsService/Search, ClientCustomerID: 6773506668,  RequestID: aHlWp5WJoKexsq1uz-q9Dg, IsFault: True, FaultMessage: Status(StatusCode=""InvalidArgument"", Detail=""Request contains an invalid argument."", DebugException=""Grpc.Core.Internal.CoreErrorDetailException: {""created"":""@1607539298.518000000"",""description"":""Error received from peer ipv4:172.217.14.234:443"",""file"":""T:\src\github\grpc\workspace_csharp_ext_windows_x64\src\core\lib\surface\call.cc"",""file_line"":1062,""grpc_message"":""Request contains an invalid argument."",""grpc_status"":3}"")

[Google Ads API Forum Advisor Prod]

Hi Caihua,

The fix also went live around the time your request ID came in. If you can replicate the issue, could you send me a newer request ID?

[Caihua Du]

Hi Anash,

Unfortunately, this is still not working. Here is the latest request id from my client. Please take a look. Thanks a lot!

[2021-01-13 06:30:29Z] - Request made: Host: https://googleads.googleapis.com, Method: /google.ads.googleads.v6.services.GoogleAdsService/Search, ClientCustomerID: 6773506668,  RequestID: f05raAO6jxD3qggf1h5p4w, IsFault: True, FaultMessage: Status(StatusCode=""InvalidArgument"", Detail=""Request contains an invalid argument."", DebugException=""Grpc.Core.Internal.CoreErrorDetailException: {""created"":""@1610519429.863000000"",""description"":""Error received from peer ipv6:[2607:f8b0:400a:804::200a]:443"",""file"":""T:\src\github\grpc\workspace_csharp_ext_windows_x64\src\core\lib\surface\call.cc"",""file_line"":1062,""grpc_message"":""Request contains an invalid argument."",""grpc_status"":3}"")

On Wed, Dec 9, 2020 at 7:58 AM Google Ads API Forum Advisor Prod <adsapifor...@gmail.com> wrote:

[Caihua Du]

Hi Anash,

Can you please take a look and let me know if you have any findings?

To me this is a P0 bug that the status predict does not support NOT_IN syntax. 

[Google Ads API Explorer]

Hi,

I am also facing same.

 SELECT change_event.resource_name, change_event.change_date_time, change_event.change_resource_name, change_event.user_email, change_event.client_type, change_event.change_resource_type, change_event.old_resource, change_event.new_resource, change_event.resource_change_operation, change_event.changed_fields FROM change_event WHERE change_event.change_date_time >= 20210108 AND change_event.change_date_time < 20210115 ORDER BY change_event.change_date_time DESC LIMIT 10000

ApiException was thrown with message '{ "message": "Stream removed", "code": 2, "status": "UNKNOWN", "details": [] }'.   

[Google Ads API Forum Advisor Prod]

Hi,

The "stream removed" issue is most likely unrelated to this issue. Could you kindly open an issue with the client library that you are using if this issue is consistently replicable?

[Caihua Du]

Hi team,

Can you please let us know who can help with this? This issue is blocking us to use Google Ads API and we have reported for more than 2 months. 

Your help is highly appreciated, thank you!

Caihua.

[Caihua Du]

Thank you for looking into this, Anash!

I think the confusion part is that we are able to use those two Enum values from interactive query builder, so we thought this should be a valid query (please check the screenshot below).

Also from the public documentation we don't see any specific limitation of those two Enum value: label  |  Google Ads API  |  Google Developers

We can update our code to remove those Enum value from the filter, can we please update the doc so that we have more clear guidance going forward? Thank you!

On Thu, Jan 21, 2021 at 11:48 AM Google Ads API Forum Advisor Prod via Sales & Orders <notifi...@sales--orders.intercom-mail.com> wrote:

This message was sent to the following 2 people: Caihua Du, adwor...@googlegroups.com. Replying to this email will notify them.

Hi Caihua, I looked at the logs for your request. The issue is that you cannot use UNKNOWN and UNSPECIFIED enum values when filtering. You should modify your query to not filter on those enum values. The IN and NOT IN query conditions should work fine on the label status fields. Cheers Anashhttps://google-dev-relations.my.salesforce.com/servlet/servlet.ImageServer?oid=00D1U000001174p&esid=0184Q00001BiyvR&from=ext ref:_00D1U1174p._5004Q27uEVS:ref

On Wed, Jan 20, 2021 at 06:44 PM, "Caihua Du" <duca...@gmail.com> wrote:

Hi team, Can you please let us know who can help with this? This issue is blocking us to use Google Ads API and we have reported for more than 2 months. Your help is highly appreciated, thank you! Caihua.

On Tue, Jan 19, 2021 at 12:13 AM, "Caihua Du" <duca...@gmail.com> wrote:

Hi Anash,

Can you please take a look and let me know if you have any findings? To me this is a P0 bug that the status predict does not support NOT_IN syntax.

https://google-dev-relations.my.salesforce.com/servlet/servlet.ImageServer?oid=00D1U000001174p&esid=0184Q00001B0cKB&from=ext ref:_00D1U1174p._5004Q27uEVS:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to adwor...@googlegroups.com To unsubscribe from this group, send email to adwords-api...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/tKTH9000000000000000000000000000000000000000000000QL2XP300TI8Ds17sQX6_AqXoSr_sow%40sfdc.net.

[Google Ads API Forum Advisor Prod]

Hi Caihua,

Thanks for your feedback, I have filed requests with the respective teams to fix the Query builder tool and the reference documentation.