Internal error when listing batch job results

[Paweł Ulita]

Hi,

In some situations we're getting the following exception when we try to list batch job results.

_InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.INTERNAL
details = "Internal error encountered."
debug_error_string = "{"created":"@1644488186.171075445","description":"Error received from peer ipv4:74.125.140.95:443","file":"src/core/lib/surface/call.cc","file_line":1063,"grpc_message":"Internal error encountered.","grpc_status":13}"
>

Before we receive this error, we're able to fetch a round number of results, usually a multiple of 1000, even when the chunk size is lower than 1000 (10 or even 1).

We're using the Python Google Ads Library v14.1.0 and Google Ads API v9.

How can we prevent this from happening?

[Matthew Cloy]

I have seen the same error today with generating forecast and historical results. It seems random, but works 1/10 times.

[Google Ads API Forum Advisor]

Hi everyone,

Thank you for bringing this to our attention. What this support channel can do is take a look at the request and response logs of API communication that are privately sent to us. Here's logging instructions the requested logs can be generated when setting the log level to 'DEBUG'.  If this is specific to Python client library then you can reach out to its issue tracker.

Regards,

Aryeh Google Ads API Team

ref:_00D1U1174p._5004Q2W62XK:ref

[Paweł Ulita]

Hi Ads API team,

Is there something new known about this topic? We're still struggling with this problem (i.e. internal error when requesting batch job results). We've also seen a very similar error in other batch-job related situations, for example when creating or running batch jobs.

Just as you requested, I followed up with a private message with the logs you requested, and on the 14th of February you confirmed that you had received my message.

Best,

Paweł

[Arshdeep Singh Bhargav]

Hi Google Team,
We are also facing this issue with similar error while listing Batch job results.
And the issue is not limited to Python library, we use .Net and the error is still reproducible.

Kindly help us with this,

Thanks and Regards,
Arshdeep

[Arshdeep Singh Bhargav]

I have already shared detailed logs privately @Aryeh

[Google Ads API Forum Advisor]

Hi Arshdeep,

Thank you for providing the requested details. Allow me to raise the information that you provided to the team. We will revert back to you with updates when it becomes available.

Regards,

Ernie John Google Ads API Team

ref:_00D1U1174p._5004Q2W62XK:ref

[Arshdeep Singh Bhargav]

Hi Team Google,

Any updates on this?

Best,
Arsh

[Paweł Ulita]

Hi again,

We're still getting this problem every day. Is there anything new known about it?

Best,

Paweł

[Aayushi Bhandari]

Hi team.

Any updates on this issue?

Cheers,

Aayushi

[Google Ads API Forum Advisor]

Hello,

This error is on our side. The team is working on a fix for this, and I'll let you know once it's rolled out.

Regards,
Mike, Google Ads API Team

ref:_00D1U1174p._5004Q2W62XK:ref

[Jefferson Cechinel]

Hello there!

Any updates on this issue?

[Ashir Khan]

Facing the same issue in java library v9, v10 version . 
Error: io.grpc.StatusRuntimeException: INTERNAL: Internal error encountered. I also faced Deadline_Exceeded error when API are not responding against the customer id and keep it stuck and after an hour API responds deadline_exceeded error.
Api works well when we download single accounts.But when we download records against all the MCC heirarchy then throw internal or deadline_exceeded error.

[Google Ads API Forum Advisor]

Hello,

The team is still working on the fix. The issue is on our side, and doesn't depend on what client library you use.

I will let you know once I see that the fix is rolled out.

[Yogesh Patil]

Hi,

We are also facing this issue, especially when mutating a large number of order adjustments.

I will wait for this fix.

Thanks,

Yogesh

[Google Ads API Forum Advisor]

Hello - 

I'm a member of the Google Ads API team following up here to let you know that this issue has been resolved, and you should no longer be seeing these issues.

Best,

Ben Karl Google Ads API Team

ref:_00D1U1174p._5004Q2W62XK:ref