Thanks Heidi and team! I'll decrease request date range and will contact back if this won't help.
On Tuesday, August 30, 2022 at 8:04:18 PM UTC+3 adsapi wrote: > Hi, > > Thank you for reaching out to us. > > The error DEADLINE_EXCEEDED > <https://developers.google.com/google-ads/api/reference/rpc/v11/InternalErrorEnum.InternalError?hl=en#deadline_exceeded> > > indicates that your request took longer than the deadline. That said, you > may check this example > <https://developers.google.com/google-ads/api/docs/samples/set-custom-client-timeouts?hl=en> > > to set custom client timeouts and this documentation > <https://developers.google.com/google-ads/api/docs/client-libs/php/timeout?hl=en> > > for more information in timeouts. Note that you can set the timeout to 2 > hours or more, but the API may still time out extremely long-running > requests and return a DEADLINE_EXCEEDED > <https://developers.google.com/google-ads/api/reference/rpc/v11/InternalErrorEnum.InternalError#deadline_exceeded> > > error. > > Timeouts are often because what is being queried is too big to send back > to you. It appears that those accounts where this is failing contain a lot > of data. To fix this, I would suggest you decrease the size of your data > that you're requesting back by adding filtration to your queries. > > For your questions, “*My question is why could this happen to reports > which are relatively small?, What could be recommendations for us? Extend > 'timeoutMillis'? Reduce 'timeoutMillis'?, Max conversions lookback for > account we query is 90 days so we need 90 days of data. Will it be more > preferable to request 9 reports for 10 days of 3 reports for 30 days or > ...? *” > -You may try first what I suggested you do in the above response. If you > are still consistently encountering said error after the suggestions, then > you may provide us with the complete request > <https://developers.google.com/google-ads/api/docs/concepts/field-service?hl=en#request> > > and response > <https://developers.google.com/google-ads/api/docs/concepts/field-service?hl=en#response> > > logs with the request-id > <https://developers.google.com/google-ads/api/docs/concepts/call-structure?hl=en#request-id> > > , so our team can better check. > > For the PHP client library, logging can be enabled by navigating to this > Logging > documentation. > <https://developers.google.com/google-ads/api/docs/client-libs/php/logging> > > You may then send the requested information via the Reply privately to > author option. If this option is not available, you may send the details > directly to our googleadsa...@google.com alias instead. > > Best regards, > [image: Google Logo] > Heidi > Google Ads API Team > > > ref:_00D1U1174p._5004Q2dtHAp: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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com 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 adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/19dec091-f51b-40eb-a2d9-c19f09148958n%40googlegroups.com.
