DEADLINE_EXCEEDED eror

330 views
Skip to first unread message

Dinesh...@sony.com

unread,
Mar 4, 2021, 9:01:25 PM3/4/21
to adwor...@googlegroups.com
We have been seeing this error a few times in the last 24 hours:
io.grpc.StatusRuntimeException: DEADLINE_EXCEEDED: deadline exceeded after 3599.999896769s. [buffered_nanos=32242497, remote_addr=googleads.googleapis.com/172.217.14.202:443]

The error has appeared in these Customer Ids: 2643252297, 3739980559

We are using Google Ads API Java Client Library v5.

Thanks



DEADLINE_EXCEEDED error log.txt

Jack

unread,
Mar 5, 2021, 10:54:23 AM3/5/21
to AdWords API and Google Ads API Forum
Following.... Running into this too since March 2nd.

Pete Lavetsky (AdWords API Guru)

unread,
Mar 6, 2021, 12:28:13 PM3/6/21
to AdWords API and Google Ads API Forum
Same here. Started 3am EST March 3rd.

Pete

Google Ads API Forum Advisor Prod

unread,
Mar 8, 2021, 11:42:43 AM3/8/21
to pete.l...@gmail.com, adwor...@googlegroups.com
Hi All,

If you are still having an issue with the DEADLINE_EXCEEDED error, can you please reply privately with your request and response logs?

Thanks,
Matt
Google Ads API Team

Google Logo
Matt
Google Ads API Team
 


ref:_00D1U1174p._5004Q2DLLQv:ref

Pete Lavetsky (AdWords API Guru)

unread,
Mar 8, 2021, 11:51:31 AM3/8/21
to AdWords API and Google Ads API Forum
There's no reply privately option I see ... maybe only for OP?

This is 100% still happening.

I have an open ticket on the Java API bug tracker, tho it's not a Java specific problem : https://github.com/googleads/google-ads-java/issues/407

The requests are not making it to Google's servers ... looks to be a bad node somewhere on the Google network

Pete

Google Ads API Forum Advisor Prod

unread,
Mar 8, 2021, 2:44:02 PM3/8/21
to pete.l...@gmail.com, adwor...@googlegroups.com
Hi All,

Thanks again for your patience on this. This is now a known issue that has been reported by multiple users. Some users may experience a higher latency, or, as reported on this thread, a DEADLINE_EXCEEDED error. We are currently investigating the nature of this issue and we will provide an update here as soon as we can. 
Reply all
Reply to author
Forward
0 new messages