Internal Error Occurred while submitting Batch Job for Creating RSA
Samarth Gupta
While Submitting Batch Job with 10K+ Ad Group Ad Operations to create Responsive search ads per adgroups, we are getting Internal Error Occurred!
{
"errorCode": {
"internalError": "INTERNAL_ERROR"
},
"message": "An internal error has occurred."
}
The error does not seems to be transient on every apply we are getting Internal error error. Could you let us in knowing why Internal error is happening?
As per API docs https://developers.google.com/google-ads/api/docs/batch-processing/best-practices
In case of large operation we might get REQUEST_TOO_LARGE error, but for us it is always internal error.
Google Ads API and AdWords API Forum
Re-posting the last inquiry (https://groups.google.com/g/adwords-api/c/uZWbNYosSVY) from the forum as it wasn't routed to our support queue.
Regards,
Google Ads API Forum Advisor
Hi,
Thanks for reaching out to Google Ads API Support.
I see that you encountered an Internal error while submitting a Batch Job with 10K+ Ad Group Ad Operations to create Responsive search ads per AdGroups. Internal error means something unexpected happened while processing the request. The common cause of this error is that the API isn't functioning correctly due to a bug.
With regards to your concern, we can see in this document that it is recommended to add no more than 1,000 operations per AddBatchJobOperationsRequest and use the sequence_token to upload the rest of the operations to the same job. We also recommend you to follow the limitations in each BatchJob.
If the issue persist, you may then provide us the complete request and response logs with request ID generated as shown in the respective links. We do this to check if there’s an error thrown on your side and we can further investigate.
If you haven't enabled logging yet, it can be enabled by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from this link. For REST interface requests, you can enable logging via the curl command by using the -i flag. This will cause the tool to include the HTTP response headers in the output.
You may then send the requested logs via the Reply privately to author option. If the reply privately option is not available, you can send your logs directly to our googleadsa...@google.com alias instead.
Regards,
 |
Google Ads API Team |
ref:_00D1U1174p._5004Q2k03ps:ref