Hi,

same here. Some reports succeed now. But some reports don't, most likely 
related to the data size. We didn't change anything on our side, all report 
fetches worked fine with their defined date ranges before Sept 27, when the 
issue started.

The issue hasn't been fully resolved and we're still unable to fetch all 
reports via the Google Ads API. The behavior for the failing fetches is 
still the same. The iterator in the search_stream fetch gets stuck, is 
never finishing and at some point our wrapping timeout kills the task. 
Since there was no code change on our side and many developers are 
reporting the same issue here, using different programming languages, we 
assume the issue is on the Google Ads API side. My guess would be that the 
GRPC call for search_stream is not properly ended. To the best of our 
knowledge and our inspection so far, this is far too low level from the 
perspective of users of the Google Ads API (developers) and needs to be 
fixed on the Google side.

Ideally please provide an ETA when the issue will be fixed on Google side. 
Also I wonder where we can best track the status of the API issue. 
https://ads.google.com/status/publisher/ continuously shows Google Ads 
operating fine, though the API clearly has severe issues for search_stream 
requests.

Thanks,

Robert
On Wednesday, 28 September 2022 at 01:49:05 UTC+2 Andrew Repp wrote:

> Hi,
>
> We are also continuing to see the same issue even after the all clear 
> message above. It appears to be related to the number of records involved.
>
> This query
>
>         SELECT
>             segments.date,customer.id,campaign.name,campaign.id
> ,campaign_criterion.bid_modifier,campaign_criterion.criterion_id,segments.device,metrics.impressions,metrics.clicks,metrics.cost_micros,metrics.gmail_forwards,metrics.gmail_saves,metrics.gmail_secondary_clicks
>         FROM
>             campaign_audience_view
>     WHERE metrics.impressions > 0 AND segments.date BETWEEN '2022-09-23' 
> AND '2022-09-27'
>
> fails with 
>
> Response
> -------
> Headers: {}
> Fault: {
>   "created": "@1664321827.318637000",
>   "description": "Error received from peer ipv4:142.250.217.74:443",
>   "file": "src/core/lib/surface/call.cc",
>   "file_line": 904,
>   "grpc_message": "Deadline Exceeded",
>   "grpc_status": 4
> }
>
> But this query
>
>         SELECT
>             segments.date,customer.id,campaign.name,campaign.id
> ,campaign_criterion.bid_modifier,campaign_criterion.criterion_id,segments.device,metrics.impressions,metrics.clicks,metrics.cost_micros,metrics.gmail_forwards,metrics.gmail_saves,metrics.gmail_secondary_clicks
>         FROM
>             campaign_audience_view
>     WHERE metrics.impressions > 0 AND segments.date BETWEEN '2022-09-26' 
> AND '2022-09-27'
>
> succeeds. Notice that by only selecting 2 days of data instead of 5, the 
> query is able to complete. Before today, the query for 5 days completed 
> successfully.
>
> Any help from the Google folks on a resolution?
>
> Thanks,
> Andrew
>
> On Tuesday, September 27, 2022 at 3:39:56 PM UTC-7 [email protected] wrote:
>
>> We're still seeing this problem when streaming a large set of keywords 
>> from a customer account. It appears the request gets stuck and eventually 
>> the process times out. We have a query as follows:
>>
>>   SELECT 
>>   ad_group_criterion.criterion_id, 
>>   ad_group_criterion.status,
>>   ad_group_criterion.keyword.match_type,
>>   ad_group_criterion.keyword.text, 
>>    ...
>>   FROM ad_group_criterion WHERE  ad_group_criterion.type = KEYWORD
>>
>> and we use the searchStream API to process the results. The result set is 
>> very large, and could exceed  100,000 keywords but up until today we never 
>> had a problem with it.
>>
>> On Tuesday, September 27, 2022 at 3:28:02 PM UTC-5 adsapi wrote:
>>
>>> Hello Everyone,
>>>
>>> Thank you so much for providing all this information! I believe the 
>>> issue that was causing this was cleared up a few hours ago. I see our 
>>> monitoring is showing that traffic is back to normal. If you continue to 
>>> have the same issue, please respond back to me.
>>>
>>> Thanks,
>>> [image: Google Logo] 
>>> Nadine Wang 
>>> Google Ads API Team 
>>>   
>>>
>>> ref:_00D1U1174p._5004Q2egwqd: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 [email protected]
To unsubscribe from this group, send email to
[email protected]
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 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/50b59bdb-7f86-42bd-a2ba-6a55006c2aebn%40googlegroups.com.
  • Re... Robert Heise
    • ... Tjadi Peeters
    • ... Tjadi Peeters
      • ... Mario GarcĂ­a
        • ... Robert Heise
          • ... Tjadi Peeters
            • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum

Reply via email to