BatchJobService changed to only return errors without applying orthogonal changes?

[Sha Liu]

Today (5/4) I noticed that if a batch job has some operations triggering some errors, only these errors are returned as the batch result, and any other orthogonal changes are not applied. I observed this with both policy validation errors and entity exceeded errors. It seems batch job service no longer allows partial errors.

Is this new behavior? From my logs it looks like the it was still the old behavior yesterday, and I cannot find any documentation for this change.

[Ivan Bautista]

Hi Sha,

As per this guide and the 201702 release notes, partial failures is still supported and is set to true by default for all requests to the BatchJobService and no specific changes have been applied for handling partial failures in the latest version. Make sure that you didn't explicitly set the partialFailure SOAP header to false. 

However, for us to investigate further, could you reply to us privately (using reply privately to author option) with the batch job IDs in question as well as your clientCustomerId?

Regards,

Ivan

AdWords API Team

[Alexey Tishchenko]

We have encountered the same problem, so the behaviour was definitely changed since 04 May 2017. 

[Alexey Tishchenko]

Hi Ivan,

I've just tried to run a test job with ID = 491407866 - create 2 keywords, one of them contains invalid character. That results in the response containing only erroneous object - the correct keyword was not created. I've tried to run it with and without implicit "partialFailure" SOAP header but it did not make any difference at all. So, from my point of view, the behaviour was definitely changed and it is not possible to make it acting like before.

Regards,

Alexey Tishchenko

[Josh Radcliff (AdWords API Team)]

Hi Alexey, Sha,

Some other users pointed out similar problems in a separate post, and the team is working on resolving these issues. I'll reply back here once I have more information.

Thanks,

Josh, AdWords API Team

[Josh Radcliff (AdWords API Team)]

Hi,

A fix has been applied and batch jobs should now behave as expected. Please let me know if you see this issue occur again on new jobs.

Thanks,

Josh, AdWords API Team