Reporting error on response size (using searchStream)

[j.e.frank]

We are running reports through the Ads API in Java, and using searchStream as suggested in the documentation.  However, for certain kinds of reports (usually a daily report) we are hitting an error with the gRPC response size.

Based on the documentation, I was expecting that using searchStream would not have this problem.

The specific error message also makes me wonder if the Java client is using the 4MB gRPC limit as opposed to the 64MB limit mentioned in the documentation.  Here is an example error message status:

Status: Status{code=RESOURCE_EXHAUSTED, description=gRPC message exceeds maximum size 4194304: 5299161, cause=null}

It is the 4194304 that makes me wonder about the 4MB limit.  We are on on v10 of the Java library.

We can address this by requesting smaller date ranges and stitching together the results later, but I wonder if a) we are doing something wrong, or b) if we can fix this in another way.

-Jason

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to us.

As per the guide , the (Java) client library should use the 64 mb limit. However, based on the error :

Status: Status{code=RESOURCE_EXHAUSTED, description=gRPC message exceeds maximum size 4194304: 5299161, cause=null}

This then appears to be more of a client library related issue. I would recommend that you reach out to the client library owners via this link , to clarify what maybe causing the size error.

Should they determine that there are no issues in the client library, you may provide our team with the complete request and response logs, and the request-id , generated when the error occurred. 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,

Heidi Google Ads API Team

ref:_00D1U1174p._5004Q2XnLxe:ref