Limit on ListingGroup operations in a BatchJob still in place

[Miquel Isern Roca]

Hello,

with the move to the GoogleAds API, a limit on the number of operations allowed inside a BatchJob for ListingGroups was applied. Back then the limit was 1000 operations in a BatchJob. That was reportedly fixed already.

Link to an old post I opened about the problems caused by that limit.

I was recently checking if the limit was indeed gone. And my tests indicate that there's still a limit on the number of operations.

When I try to create a tree of 19_000 ListingGroups for an AdGroup using a Batch Job all my ListingGroup operations come back with an error like this one:

status {
  code: 10
  message: "The MutateJob was aborted. There are no further results to return."
  details {
    [type.googleapis.com/google.ads.googleads.v11.errors.GoogleAdsFailure] {
      errors {
        error_code {
          internal_error: INTERNAL_ERROR
        }
      }
    }
  }
}

Tests with a smaller number of ListingGroup operations succeed. If the maximum number of ListingGroup nodes in a tree is 20_000, why is the limit of ListingGroup operations allowed in a BatchJob lower than that?

Is there a reason? Will this limit be removed at some point?

Thanks.

[Google Ads API and AdWords API Forum]

Re-posting the last inquiry (https://groups.google.com/g/adwords-api/c/6rd7AGkjO0E) from the forum as it wasn't routed to our support queue.

Kind regards,
Carmela

Google Ads API Team

[Google Ads API Forum Advisor]

Hi,
 

Thank you for notifying our team about the issue you encountered.
 

So our team can better investigate the errors, could you share as well the generated request and response logs, and its request-id? In addition, could you also share any batch job IDs generated by your requests? If you haven't yet, logging can be enabled by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation.

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.
 

Regards,

Darwin Google Ads API Team

ref:_00D1U1174p._5004Q2hxZRz:ref

[Google Ads API Forum Advisor]

Hi Miquel,

Thank you for your reply and for the logs you have attached.

Unfortunately, however, the logs that you sent over does not appear to contain the details of the internal error. That said, could you share the logs that contain the internal error and the request-id that was returned with it?

Our team will need these details so we can raise this issue for further investigation.

Best regards,

Peter Laurence Google Ads API Team

ref:_00D1U1174p._5004Q2hxZRz:ref

[Google Ads API Forum Advisor]

Hi Miquel,

Thank you for providing the requested details. I am Carmela from the Google Ads API support team as well. 

With regards to the error that you've encountered, the said error means that Google Ads API encountered an unexpected internal error. This is one of the retryable errors which can indicate a temporary problem that may be resolved by retrying the request after a short pause. Can you confirm if you tried retrying your request and still got the INTERNAL_ERROR error?

In addition, allow me to raise this issue to the rest of our team to better check why you are getting the said error. Rest assured that we will get back to you for updates.

Regards,

Carmela Google Ads API Team

ref:_00D1U1174p._5004Q2hxZRz:ref

[Google Ads API Forum Advisor]

Hi Miquel,

I think this is a different issue caused by the size of the request, rather than a hard enforced limit. I've asked the team to investigate, but I think a slightly smaller tree size should go through without any issues.
 

Regards
Anash 

ref:_00D1U1174p._5004Q2hxZRz:ref

[Miquel Isern Roca]

Hello again,

to answer Caramela, I indeed tried and retried sending the operations multiple times on different days even. That's why I ended up opening the issue.

Regarding your answer Anash, I'm aware that the size is the issue because sending a smaller amount of ListingGroups operations ( i think under 10k) works. 

My question is why this is so?

A ListingGroup tree has a limit of 20_000 nodes ( it is smaller for the new PerformanceMax but not for normal Shopping Campaigns). And the limit of operations that fit in a BatchJob in the new API goes up to a million. If that's the case why am I not able to send the 20_000 operations to create a single tree in a single BatchJob?

Regards,

Miquel Isern Roca Python Software Engineer +44 (0)20 331 800 89

[Miquel Isern Roca]

Hello,

do you have any updates on this issue?

Thanks,

Miquel Isern Roca Python Software Engineer +44 (0)20 331 800 89

[Google Ads API Forum Advisor]

Hi Miquel,

No updates since our last email on January 20. 

[Miquel Isern Roca]

Hello again,

As suggested by your side, I have been trying to push ListingGroups bigger than 10_000 nodes and can't get it to work with a single BatchJob. All the operations always come back with an INTERNAL_ERROR with the message: "The MutateJob was aborted. There are no further results to return.". 

A ListingGroup tree has a limit of 20_000 nodes ( it is smaller for the new PerformanceMax but not for normal Shopping Campaigns). And the limit of operations that fit in a BatchJob in the new API goes up to a million. If that's the case why am I not able to send the 20_000 operations to create a single tree in a single BatchJob?

Are you planning to work on a solution for this? We currently don't have a solution that allows us to send trees bigger than 10_000 nodes which are supposed to be valid.

Regards,

Miquel Isern Roca Python Software Engineer +44 (0)20 331 800 89

[Google Ads API Forum Advisor]

Hi Miquel,

I still don't have much updates from the team, but I've pinged them for progress. Meanwhile, any newer job IDs could be helpful in checking whether these are the same issues or different ones.