Same here
[image: latency.PNG]

I did notice that, when the server-side timeout occurs, the error changed.
 
Sep 27, 02:31 CEST:
*Status(StatusCode="Unknown", Detail="Stream removed", 
DebugException="Grpc.Core.Internal.CoreErrorDetailException: 
{"created":"@1664238664.220000000","description":"Error received from peer 
ipv4:216.58.214.10:443","file":"..\..\..\src\core\lib\surface\call.cc","file_line":1070,"grpc_message":"Stream
 
removed","grpc_status":2}")* 

Sep 28, 02:30 CEST:
*Status(StatusCode="Internal", Detail="Received RST_STREAM with error code 
2", DebugException="Grpc.Core.Internal.CoreErrorDetailException: 
{"created":"@1664325053.844000000","description":"Error received from peer 
ipv4:142.250.179.170:443","file":"..\..\..\src\core\lib\surface\call.cc","file_line":1070,"grpc_message":"Received
 
RST_STREAM with error code 2","grpc_status":13}")* 

This was from the same GAQL query, on the same CustomerId.


On Wednesday, September 28, 2022 at 9:02:47 AM UTC+2 
[email protected] wrote:

> Hi,
>
> We are still running into the same issue for large reports (our small ones 
> never stopped working either).
>
> Kind regards,
>
> Op woensdag 28 september 2022 om 07:51:40 UTC+2 schreef 
> [email protected]:
>
>> Hello,
>>
>> Also for us, the large reports still fail. With HTTP requests or with the 
>> client library in the ads to bq dataflow pipeline.
>>
>> Smaller reports do work, but they never stopped working on our end.
>>
>> On Wednesday, September 28, 2022 at 6:30:40 AM UTC+2 Robert Heise wrote:
>>
>>> Hi,
>>>
>>> still having the same issue. Some reports finish, most of them don't, 
>>> search_stream requests not finishing and getting stuck.
>>>
>>> Please provide an ETA when the issue will be resolved on Google side.
>>>
>>> Thanks,
>>>
>>> Robert
>>>
>>> On Tuesday, 27 September 2022 at 22:29:44 UTC+2 adsapi wrote:
>>>
>>>> Greetings!
>>>>
>>>> Thanks for providing the information. You should see traffic coming 
>>>> back to normal with your errors returning to normal levels. The issue that 
>>>> caused this has been resolved. Please get back to me if you continue to 
>>>> see 
>>>> issues.
>>>>
>>>> Thanks,
>>>> [image: Google Logo] 
>>>> Nadine Wang 
>>>> Google Ads API Team 
>>>>   
>>>>
>>>> ref:_00D1U1174p._5004Q2egxrU: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/271fb782-048e-450d-955d-0a3e8e00336cn%40googlegroups.com.
  • Pe... Zweitze
    • ... Ales Sturala
      • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
        • ... Tjadi Peeters
        • ... Zweitze
          • ... Robert Heise
            • ... Tjadi Peeters
              • ... Zweitze
                • ... Filipe
                • ... 'Ronald Findling' via Google Ads API and AdWords API Forum
                • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
                • ... 'Thomas Vincent-Sweet' via Google Ads API and AdWords API Forum
                • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
                • ... Robert Heise
                • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
                • ... Tanishq Hooda
                • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum

Reply via email to