Peter, Do you locally store the response IDs given to successfully added criterion? If so, do you have a value for the criterion addition?
Assuming the preceding calls actually did succeed, it is possible your chain of mutations each hit different end points and there was some server side latency, causing the criterion ID passed in not to exist on the box you hit. I operate in much the same way and have never run into this problem, but I do have a bit of built in latency ( just a second or two ) on my end that may have helped avoid this all along. BulkMutateJobService may be valuable to you : http://code.google.com/apis/adwords/docs/reference/latest/BulkMutateJobService.html Pete -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
