Hi, I believe we discussed this problem offline. The short answer is that the behavior listed is expected, except that the batches should remain in the same order. Also, we encourage developers to not depend on any defined batch size, as this may change over time.
Best, - Eric Koleda, AdWords API Team On Mar 18, 1:04 pm, btaz <msund...@gmail.com> wrote: > I've read that an atomic batch size currently is set to 50. > > I setup a test that performs 150 AdGroup Criterion operations in > total. The first 50 operations were rigged to fail, the following 50 > operations to be successful, and the last 50 operations to fail. > For each operation (in this case pause keywords) I had to provide an > AdGroup ID and a Criterion ID). > > The result from the AdWords bulk mutate job service was: > > One FailureResult object containing an EntityNotFound exception and > the AdGroupID's (50 of them) that caused the failure with a batch > relative index. > > 49 BatchFailureResult objects that doesn't contain any AdGroup > Critetion identifying information. > > One FailureResult object containing an EntityNotFound exception and > the AdGroupID's (50 of them) that caused the failure with a batch > relative index. > > 49 BatchFailureResult objects that doesn't contain any AdGroup > Critetion identifying information. > > 50 ReturnValueResult objects containing the AdGroup ID, Criterion ID > and status for all pause keyword operations that were successful > > Since the results comes back in a different order (batches that failed > due to errors are returned first) how do you suggest that we identify > which input data caused the failures? Yes, I realize that using a bit > of detective work you can figure this out in most cases, but I'd > prefer to build a programmatic solution that isn't too complex. > > Unless I missed something the current implementation makes it > difficult to identify which operations that were successful and which > operations that failed when an atomic batch failed, especially when > multiple batches fails within the same OperationStream. > > If you for example would have provided both the AdGroup ID and the > Criterion ID in the EntityNotFound exception it would have been a > fairly trivial exercise to map the failures against the input > operations, something that the current implementation makes > unnecessarily difficult. > > What is the Google AdWords teams recommended solution for how to > properly identify the operations that failed in cases like this? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Have you migrated to v200909 yet? The v13 sunset is on April 22, 2010. Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en To unsubscribe from this group, send email to adwords-api+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
