user_interest query returns "Internal error occurred" response

[Techsupport L2L]

Hi,

I am using below query to get user interests but since yesterday it is returning "Internal error occurred."

SELECT
                   user_interest.availabilities,
                    user_interest.name,
                    user_interest.resource_name,
                    user_interest.user_interest_parent
                FROM user_interest
                WHERE
                user_interest.taxonomy_type IN ("AFFINITY", "IN_MARKET") AND
                user_interest.name LIKE "%real estate%"

Can you please let me know what is wrong with this and help me to fix this issue?

[Google Ads API Forum Advisor]

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 occurs when something unexpected happens while processing the request. You can refer to the documentation, to know how to handle the  Internal Error.

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 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 and response with request-id and request header) 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, .Net, PHP, Python, Ruby or Perl 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,
 

Google Ads API Team

[Christopher Hronek]

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.

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

After reviewing your concern, I understand that you are encountering the "INTERNAL_ERROR" while trying to fetch data using the queries via the Google Ads API searchStream method.

Kindly note that the INTERNAL_ERROR occurs when something unexpected happened while processing the request. The common cause could be that the API isn't functioning correctly due to a bug. However, this is transient in nature and the issue may be resolved by retrying the request after a short pause. You may retry any requests that failed with this error, using an exponential backoff schedule for the retries. Here is a code example demonstrating how to implement an exponential back off strategy.

Also, note that I am able to replicate this issue at my side. So, kindly allow me to check this with the rest of our team and one of our colleagues will reach out to you once we have an update. Meanwhile, your patience is highly appreciated. 

[Alberto]

Hi guys,

We are also affected by this bug as stated on https://groups.google.com/g/adwords-api/c/ageefJ086Zo

Please, let us know when this is fixed on google ads api side.

Thanks.

[Google Ads API Forum Advisor]

Hi,

Thanks for bringing this issue to our attention. The team is actively working on a fix to address this.

Thanks again for your patience. I will get back to this message thread once I have an update.

[Alberto]

Hi,

Any updates on this?

Thanks