BatchJobs for specific customer stuck in PENDING status

[Miquel Isern Roca]

Hello,

we manage a customer GoogleAds account that hasn't been able to run the submitted BatchJobs since the 28th October at 9AM. The last BatchJob that ran successfully according to the Change History did that the 28th October, 8:41:38

Currently, it has a backlog of a 100 BatchJobs all in PENDING status. I can't see any information in the customer's account as to why that might be.

The MutateRequests sent to the account are processed as expected.

Can we figure out why this is happening and get the BatchJobs running again?

Thanks

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

I understand that you are observing a 'PENDING' status for about 100 batch jobs from 28th October.

I would recommend you refer to this document on 'Best Practices and Limitations' for guidelines when using BatchJobService.

Note that we don't have much information for the investigation. So, to assist you further, please provide us with the complete API logs (request and response with request-id and request header) generated for the batch job requests where you observe the said behavior.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

You can send the details via Reply privately to the author option, or direct private reply to this email.

 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGhh5:ref" (ADR-00274053)

Thanks,
 

Google Ads API Team

[Miquel Isern Roca]

Hello,

thanks for the reply. This issue turned out to be on our side. We had a code path that could end up creating a BatchJob, failing to upload any operations to it and try that same thing again without removing the created and empty BatchJob leaving a zombie in the queue.

Thanks and apologies