BatchJobService returning inconsistent job results

[Dorian Kind]

Hi all,

starting yesterday, we've noticed that the BatchJobService result list doesn't exactly correspond to the actual operations that we send. More specifically, it appears that some operations are not being included in the result. What makes it worse is that the "index" field of the results that actually are returned does not refer to the right operation, making it impossible to find out which of your operations actually failed. So far we haven't found any sort of pattern as to which type of operations do not give a result.

As an example, today we sent a job containing 239'131 operations, but the results XML file only had 224'779 "rval" entries. The job ID should be 491045429.

Has anyone else experienced this? API advisors, is this a known issue?

Thanks and best regards,

Dorian

[Dorian Kind]

Seems to be the same issue that was reported here: https://groups.google.com/forum/#!topic/adwords-api/aAJ7i2BPdLk

[Stefano Fontana]

Same here. Job ID 491139160

It seems that the problem arises when you use temporary IDs (i.e. creating adgroups and ads in the same batch job) .

[Konstantin Tarassow]

We also have this problem since yesterday.

[Stefano Fontana]

It also happens when submitting a batch that contains operations that cause violations.

The worst part is that not even the good ones go through and good ads are not created.

Please have a look at this, asap :(