Pete, thanks for your help.
We do store those IDs. The SOAP xml response from the criterion addition (which triggers the error) is the following: <?xml version="1.0" encoding="UTF-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> <soap:Header> <ResponseHeader xmlns="https://adwords.google.com/api/adwords/cm/v201109";> <requestId>0004bbbcd0b9e0b80a3460a100000df8</requestId> <serviceName>AdGroupCriterionService</serviceName> <methodName>mutate</methodName> <operations>1</operations> <responseTime>357</responseTime> <units>15</units> </ResponseHeader> </soap:Header> <soap:Body> <mutateResponse xmlns="https://adwords.google.com/api/adwords/cm/v201109";> <rval> <ListReturnValue.Type>AdGroupCriterionReturnValue</ListReturnValue.Type> <value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:type="BiddableAdGroupCriterion"> <adGroupId>3484052224</adGroupId> <criterion xsi:type="Keyword"> <id>30808583</id> <type>KEYWORD</type> <Criterion.Type>Keyword</Criterion.Type> <text>test keyword 1</text> <matchType>BROAD</matchType> </criterion> <AdGroupCriterion.Type>BiddableAdGroupCriterion</AdGroupCriterion.Type> <userStatus>PAUSED</userStatus> <systemServingStatus>ELIGIBLE</systemServingStatus> <approvalStatus>PENDING_REVIEW</approvalStatus> <bids xsi:type="ManualCPCAdGroupCriterionBids"> <AdGroupCriterionBids.Type>ManualCPCAdGroupCriterionBids</AdGroupCriterionBids.Type> <maxCpc> <amount> <ComparableValue.Type>Money</ComparableValue.Type> <microAmount>10000</microAmount> </amount> </maxCpc> <bidSource>CRITERION</bidSource> <enhancedCpcEnabled>false</enhancedCpcEnabled> </bids> <firstPageCpc> <amount> <ComparableValue.Type>Money</ComparableValue.Type> <microAmount>2500000</microAmount> </amount> </firstPageCpc> <qualityInfo> <isKeywordAdRelevanceAcceptable>true</isKeywordAdRelevanceAcceptable> <isLandingPageQualityAcceptable>true</isLandingPageQualityAcceptable> <isLandingPageLatencyAcceptable>true</isLandingPageLatencyAcceptable> <qualityScore>3</qualityScore> </qualityInfo> </value> </rval> </mutateResponse> </soap:Body> </soap:Envelope> We already had a server latency issue in mind and we are definitely considering BulkMutateJobService for the future. Regards, Peter Am Mittwoch, 21. März 2012 17:14:00 UTC+1 schrieb Pete Lavetsky (AdWords API Guru): > > 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
