We've also been dealing with this same error when querying user_interest
for the past 2 days. Prior to that our data pipelines that were extracting
from this endpoint were just fine.
*Request*
Request: customer_id: "7219273531" query:
"SELECT\n\tuser_interest.availabilities,\n\tuser_interest.user_interest_id,\n\tuser_interest.launched_to_all,\n\tuser_interest.name,\n\tuser_interest.resource_name,\n\tuser_interest.taxonomy_type,\n\tuser_interest.user_interest_parent\nFROM
user_interest" page_size: 1000
*Response*
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated
with: status = StatusCode.INTERNAL details = "Internal error encountered."
debug_error_string = "UNKNOWN:Error received from peer
ipv4:142.251.33.106:443
{created_time:"2024-02-14T18:45:26.389808369+00:00", grpc_status:13,
grpc_message:"Internal error encountered."}" >
*Request ID*jXtahoI6bm8aGGMmduT67g
*Request Header*
Headers: { "developer-token": "REDACTED", "login-customer-id":
"7543661243", "x-goog-api-client": "gl-python/3.10.13 grpc/1.59.2
gax/2.17.0 gccl/23.0.0 pb/4.25.2", "x-goog-request-params":
"customer_id=7219273531" }
Other messages on this Google Group are also leading me to believe that
it's an issue with the Google Ad Words API...not with how we're making the
actual request.
On Wednesday, February 14, 2024 at 4:36:09 AM UTC-7 Google Ads API Forum
Advisor wrote:
> Hi,
>
> Thank you for reaching out to the Google Ads API support team.
>
> By reviewing your concern, I understand that you are getting an Internal
> Error. Kindly note *Internal Error*
> <https://developers.google.com/google-ads/api/reference/rpc/v14/InternalErrorEnum.InternalError?hl=en#internal_error>
> occurs
> when something unexpected happens while processing the request. You can
> refer to the documentation, to know how to handle the *Internal Error*
> <https://developers.google.com/google-ads/api/docs/best-practices/common-errors#internalerror:~:text=layer%20limitations.-,INTERNAL_ERROR,-Summary>
> .
>
> When you retry requests, use an exponential backoff policy. For example,
> if you first pause 5 seconds before the first retry, you could pause 10
> seconds after the second and 20 seconds after the third retry. Exponential
> backoff
> <https://developers.google.com/google-ads/api/docs/best-practices/error-types#:~:text=When%20you%20retry%20requests%2C%20use%20an%20exponential%20backoff%20policy.%20For%20example%2C%20if%20you%20first%20pause%205%20seconds%20before%20the%20first%20retry%2C%20you%20could%20pause%2010%20seconds%20after%20the%20second%20and%2020%20seconds%20after%20the%20third%20retry.%20Exponential%20backoff%20helps%20ensure%20you%20are%20not%20calling%20the%20API%20too%20aggressively.>
> helps
> ensure you are not calling the API too many times.
>
> Also, in order to debug the issue, provide us with the updated complete
> API logs (request
> <https://developers.google.com/google-ads/api/docs/concepts/field-service#request>
> and response
> <https://developers.google.com/google-ads/api/docs/concepts/field-service#response>
> with request-id
> <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id>
> and request header
> <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers>)
>
> 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
> <https://developers.google.com/google-ads/api/docs/client-libs/java/logging>
> , .Net
> <https://developers.google.com/google-ads/api/docs/client-libs/dotnet/logging>
> , PHP
> <https://developers.google.com/google-ads/api/docs/client-libs/php/logging>
> , Python
> <https://developers.google.com/google-ads/api/docs/client-libs/python/logging>
> , Ruby
> <https://developers.google.com/google-ads/api/docs/client-libs/ruby/logging>
> or Perl
> <https://developers.google.com/google-ads/api/docs/client-libs/perl/logging>
> to
> enable logging at your end. For REST interface requests, you can enable
> logging via the curl command by using the -i flag.
>
> You can send the details via *Reply privately to the author option*, or
> *direct
> private reply* to this email.
>
> This message is in relation to case "ref:!00D1U01174p.!5004Q02rz6B3:ref"
>
> Thanks,
>
> [image: Google Logo] Google Ads API Team
>
>
>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/93765db5-c2b2-4720-b7ef-c54e7fe3fd9bn%40googlegroups.com.
