BatchJobService always failing with BatchJobProcessingError.INTERNAL_ERROR

45 views
Skip to first unread message

Afaq Ansari

unread,
Aug 28, 2019, 3:37:18 AM8/28/19
to AdWords API and Google Ads API Forum
Hi,

I am trying to create ad group criterion but I keep getting following

```
...
'processingErrors': [
        {
            'fieldPath': None,
            'fieldPathElements': [],
            'trigger': None,
            'errorString': 'BatchJobProcessingError.INTERNAL_ERROR',
            'ApiError.Type': 'BatchJobProcessingError',
            'reason': 'INTERNAL_ERROR'
        }
    ],
..

```

when I get the initiated batch job. Batch job id for reference is 1834337818. Can someone please check the logs and let me know about the issue. Is it something related to my account?


Regards,
Afaq Ansari

Google Ads API Forum Advisor Prod

unread,
Aug 28, 2019, 6:29:22 AM8/28/19
to adwor...@googlegroups.com

Hi,

Thanks for posting your concern.

So that I can discuss your issue with the rest of the team, could you please help me with your customer ID and the complete SOAP request and response logs together with the error message? If you haven't enable the SOAP logging, you may refer to 'readme' section of the corresponding client library that you are using (please see this link for client libraries). 

Regards,
Ejay
Google Ads API Team



ref:_00D1U1174p._5001UHEuKq:ref

Afaq Alam Ansari

unread,
Aug 28, 2019, 12:11:23 PM8/28/19
to AdWords API and Google Ads API Forum
Hi Ejay,

Thanks for your response. I wasn't aware of enabling SOAP logging. Thanks for letting me know. The batches were failing with the same error all the time but when I tried to run with SOAP logging enabled, it doesn't fail anymore. Thus I am unable to get you the exact logs for failing batch. I'll post the logs to this same thread if it fails again in future.

Thanks for your help.

Regards.
Afaq Ansari

Google Ads API Forum Advisor Prod

unread,
Aug 28, 2019, 10:46:31 PM8/28/19
to adwor...@googlegroups.com
Hi Afaq,

Glad your issue has been fixed. Feel free to write back should the issue arise again.

Regards,
Dannison
Reply all
Reply to author
Forward
0 new messages