GRPC call fail with outstanding reads

103 views
Skip to first unread message

Himanshu Patel

unread,
Jan 3, 2025, 7:04:47 PM1/3/25
to Google Ads API and AdWords API Forum
W, [2025-01-03T08:48:37.354177 #596] WARN -- : CID: REDACTED, Host: googleads.googleapis.com:443, Method: /google.ads.googleads.v16.services.GoogleAdsService/SearchStream, IsFault: yes, Request ID: N/AI, [2025-01-03T08:48:37.354365 #596] INFO -- : Outgoing request: Headers: {"developer-token":"REDACTED","login-customer-id":"REDACTED","x-goog-api-client":"gl-ruby/3.1.4 gccl/27.0.0 gax/0.21.1 gapic/27.0.0 grpc/1.62.0 pb/3.25.5","x-goog-request-params":"customer_id=REDACTED"} Payload: {"customerId":"REDACTED","query":"SELECT ad_group.id, ad_group_ad.ad.id, ad_group_ad.ad.name, ad_group_ad.ad.type, ad_group_ad.status, ad_group_ad.ad.display_url, ad_group_ad.ad.final_urls, ad_group_ad.ad.device_preference, ad_group_ad.primary_status, ad_group_ad.primary_status_reasons, ad_group_ad.ad.text_ad.headline, ad_group_ad.ad.text_ad.description1, ad_group_ad.ad.text_ad.description2, ad_group_ad.ad.image_ad.image_url, ad_group_ad.ad.image_ad.preview_image_url, ad_group_ad.ad.image_ad.pixel_height, ad_group_ad.ad.image_ad.pixel_width, ad_group_ad.ad.expanded_text_ad.headline_part1, ad_group_ad.ad.expanded_text_ad.headline_part2, ad_group_ad.ad.expanded_text_ad.headline_part3, ad_group_ad.ad.expanded_text_ad.description, ad_group_ad.ad.expanded_text_ad.description2, ad_group_ad.ad.expanded_text_ad.path1, ad_group_ad.ad.expanded_text_ad.path2, ad_group_ad.ad.responsive_search_ad.headlines, ad_group_ad.ad.responsive_search_ad.descriptions, ad_group_ad.ad.responsive_search_ad.path1, ad_group_ad.ad.responsive_search_ad.path2, ad_group_ad.ad.legacy_responsive_display_ad.marketing_image, ad_group_ad.ad.legacy_responsive_display_ad.square_marketing_image, ad_group_ad.ad.legacy_responsive_display_ad.business_name, ad_group_ad.ad.legacy_responsive_display_ad.long_headline, ad_group_ad.ad.legacy_responsive_display_ad.short_headline, ad_group_ad.ad.expanded_dynamic_search_ad.description FROM ad_group_ad WHERE segments.date BETWEEN '2024-12-29' AND '2024-12-29' AND metrics.impressions > 0"} I, [2025-01-03T08:48:37.354464 #596] INFO -- : Incoming response (errors): GRPC::Core::CallError(grpc_call_start_batch failed with outstanding read or write present (code=8)): called from: /home/deploy/.rvm/gems/ruby-3.1.4/gems/activesupport-6.1.7.8/lib/active_support/logger_thread_safe_level.rb:67:in `add' /home/deploy/.rvm/gems/ruby-3.1.4/gems/grpc-1.62.0-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:169:in `run_batch': grpc_call_start_batch failed with outstanding read or write present (code=8) (GRPC::Core::CallError)


I see when I do query with lesser number of select fields, it returns response. 
I tried by doing only 1 Day in date range (29 Dec 2024) and also with `LIMIT 1`.
GRPC Timeout: 20 min

Please Help
Thanks

Google Ads API and AdWords API Forum

unread,
Jan 6, 2025, 8:13:29 AM1/6/25
to Google Ads API and AdWords API Forum
Hi,

Thank you for reaching out to the Google Ads API support team.

From the provided information which indicates that the query contains multiple fields, which may be causing the error. To troubleshoot this, consider breaking down the query into smaller groups.

If the issue still persists, kindly provide the complete API logs (request and response with request-id and request header) generated at your end when you are creating click conversations. Please note that logs are crucial to replicate and address your issue.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guide Ruby to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

Also, note that you are using 'v16' which is deprecated. I would suggest you upgrade to the latest version, 'v18', as soon as possible to benefit from new features. You may refer to this documentation on deprecation and sunset for more information regarding the specific deprecation and sunset dates for each available version

You can send the details via Reply privately to the author option, or direct private reply to this email.

Thanks,
The Google Ads API Team.
Message has been deleted
Message has been deleted

Google Ads API Forum Advisor

unread,
Jan 15, 2025, 1:59:50 PM1/15/25
to adwor...@googlegroups.com

Hi,

As we informed you earlier, you are using 'v16' which is deprecated. I would recommend you to upgrade to latest version ‘v18’ and retry. If you are facing the same issue, share us with updated API logs (request and response logs with request-id and request header) generated at your end. 

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGw3e:ref" (ADR-00284567)

Thanks,
 
Google Logo Google Ads API Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5



Reply all
Reply to author
Forward
0 new messages