Suddenly getting "InvalidArgument" on querying ad_group_audience_view

226 views
Skip to first unread message

Zweitze

unread,
Feb 28, 2022, 6:12:57 AM2/28/22
to Google Ads API and AdWords API Forum
This query worked about two weeks ago, but not anymore:

SELECT
    campaign.id, campaign.name, campaign.serving_status, campaign.start_date,
    ad_group.id, ad_group.name,

    ad_group_criterion.criterion_id, user_list.name,
    ad_group_criterion.final_urls, ad_group_criterion.final_mobile_urls
FROM ad_group_audience_view
WHERE
    campaign.status = 'ENABLED' AND
    campaign.serving_status IN ('SERVING', 'PENDING') AND
    campaign.start_date < '20220307' AND
    ad_group.status = 'ENABLED' AND
    ad_group_criterion.status = 'ENABLED' AND
    ad_group_criterion.approval_status != 'DISAPPROVED'

The query validator thinks this query is alright.

The query is sent to the V9 endpoint.
RequestId: b10qtSYPzr0jhJ7IjggW5w
More information:
Status(StatusCode="InvalidArgument", Detail="Request contains an invalid argument.", DebugException="Grpc.Core.Internal.CoreErrorDetailException: {"created":"@1646045959.903000000","description":"Error received from peer ipv4:142.251.39.106:443","file":"..\..\..\src\core\lib\surface\call.cc","file_line":1070,"grpc_message":"Request contains an invalid argument.","grpc_status":3}")
(That IP address is not an address of ours. And we're not coding in C++)

Any idea?
I can't insert full logs, I hope this is enough information.

Zweitze

unread,
Feb 28, 2022, 8:28:54 AM2/28/22
to Google Ads API and AdWords API Forum
I upgraded the code to use V10 and the error disappeared.
Actually the query returned .... 0 rows. Very strange.

The requestId of the upgraded API call is "", without the double quotes.
Still I wonder why V9 is broken before its sunset date.

Google Ads API Forum Advisor

unread,
Feb 28, 2022, 10:41:11 PM2/28/22
to zwe...@gmail.com, adwor...@googlegroups.com
Hi Zweitze,

Thank you for posting your concern.

To investigate the issue, could you provide the complete request and response logs with request ID and request header generated on your end using v9 where we can see the error? This information can be extracted when enabling the logging of API transaction by following one of the guides below:
Java - https://developers.google.com/google-ads/api/docs/client-libs/java/logging
.Net - https://developers.google.com/google-ads/api/docs/client-libs/dotnet/logging
PHP - https://developers.google.com/google-ads/api/docs/client-libs/php/logging
Python - https://developers.google.com/google-ads/api/docs/client-libs/python/logging
Ruby - https://developers.google.com/google-ads/api/docs/client-libs/ruby/logging
Perl - https://developers.google.com/google-ads/api/docs/client-libs/perl/logging

As for v10, would you be able to provide also the complete request and response logs with request ID and request header generated on your end so that I can check the issue there?

You can provide it via Reply privately to author option. If this option is not available, then send it instead on this email address googleadsa...@google.com.

Regards,
Google Logo
Ernie John
Google Ads API Team
 


ref:_00D1U1174p._5004Q2XjtDE:ref

Zweitze

unread,
Mar 2, 2022, 4:26:32 AM3/2/22
to Google Ads API and AdWords API Forum
The information on v9 was provided.
On v10 the logs revealed something bizarre - nothing was logged. And yet the debugger show the call was made, very strange.

Zweitze

unread,
Mar 2, 2022, 12:05:16 PM3/2/22
to Google Ads API and AdWords API Forum
More information:

The query is probably wrong, when you remove the line:
     ad_group_criterion.status = 'ENABLED' AND

everything is alright. Except... the query validator thinks this query is alright, and one can filter on field ad_group_criterion.status.

About V10: This is probably an error in the dotnet library, I created an issue

Google Ads API Forum Advisor

unread,
Mar 3, 2022, 2:07:13 AM3/3/22
to zwe...@gmail.com, adwor...@googlegroups.com
Hi Zweitze,

Thank you for your replies.

Upon checking on our end I was able to replicate the behaviours you initially reported when using both the v9 and v10. My testing was performed using CURL.

However, I was not able to observe a different behaviour when removing the ad_group_criterion.status = 'ENABLED' filter. That said, could you share to our team the complete logs you generated for this scenario, since you mentioned that everything is alright when this was removed?

You may send once more the logs privately to our team.

Best regards,

Google Logo
Peter Laurence
Google Ads API Team
 


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