BatchJobProcessingError.INTERNAL_ERROR when adding campaigns

[Josh Sephton]

Hi,

I'm adding a few thousand campaigns at a time using the BatchJobService and the batch jobs keep failing with a processing error of "BatchJobProcessingError.INTERNAL_ERROR". 

If I download the results file, I see a lot of errors due to duplicate campaign names (I'm having to run the script over and over to try to get them all added) and then a bunch succeed before the job gets cancelled. I can't see anything that's malformed or might cause an internal error. Is it possible to dig into 473003405 or  473143951 or 473304030 to see what could be causing the issue?

Thanks,
Josh

[Vishal Vinayak (Adwords API Team)]

Hi Josh,

Could you please try reducing the number of operations in your job and see if you are still facing issues? You can also check out our Best Practices Guide to optimize your batch job operations. Issues related to batch job performance are sometimes intermittent, however, if you are consistently facing these issues, please let me know and I would try to work with my team to find what's causing these issues.

Regards,

Vishal, AdWords API Team

[Josh Sephton]

Hi Vishal,

I was trying with 15,000 operations previously, but I'm seeing the same behaviour with 5000 operations. Would you expect batches of this size to complete?

Thanks,
Josh

[Thanet Knack Praneenararat (AdWords API Team)]

Hello Josh,

We're investigating those three batch jobs.

Thanks for reporting. I'll contact back when we have more info.

Best,

Thanet, AdWords API Team

[Thanet Knack Praneenararat (AdWords API Team)]

Hello Josh,

It looks like you've reused the temporary ID in the same batch job.

Note that it's totally fine to use the same temporary IDs in different batch jobs.

Did you use some kinds of algorithms to map from the time stamp to negative numbers as temporary IDs?

We encourage to use just sequence number starting from -1.

Hope this help.

Best,

Thanet, AdWords API Team

On Thursday, March 30, 2017 at 9:56:44 PM UTC+9, Josh Sephton wrote:

[Josh Sephton]

Hi Thanet,

we've used a time-based ID generator because we have a number of different workers working in parallel to generate the operations. However, if we're reusing IDs in the same batch job then we're creating more operations per second than anticipated. We can increase the resolution of the IDs so there is more guarantee of uniqueness.

Thanks for digging into this for us. 

Josh

[Thanet Knack Praneenararat (AdWords API Team)]

Hi Josh,

Thanks for getting back to me.

I think that there might be other resolutions that would be able to generate IDs unique to all workers too.

But this is up to your decision. :-)

Let us know if you need help in the future.

Best,

Thanet, AdWords API Team