We recently started seeing one of our Unit tests fail related to creating
CriterionUserList
<https://developers.google.com/adwords/api/docs/reference/v201601/AdGroupCriterionService.CriterionUserList>
objects
with the AdGroupCriterionService, we are currently using v201601 of the API
and have not made any changes on our side. Have there been any changes to
this service? See below for relevant SOAP request and response.
*SOAP Request:*
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
<SOAP-ENV:Header>
<RequestHeader
xmlns="https://adwords.google.com/api/adwords/cm/v201601";>
<clientCustomerId
xmlns="https://adwords.google.com/api/adwords/cm/v201601";>REDACTED
</clientCustomerId>
<developerToken
xmlns="https://adwords.google.com/api/adwords/cm/v201601";>REDACTED
</developerToken>
<userAgent
xmlns="https://adwords.google.com/api/adwords/cm/v201601";>REDACTED
</userAgent>
<validateOnly
xmlns="https://adwords.google.com/api/adwords/cm/v201601";>false
</validateOnly>
<partialFailure
xmlns="https://adwords.google.com/api/adwords/cm/v201601";>false
</partialFailure>
</RequestHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<mutate
xmlns="https://adwords.google.com/api/adwords/cm/v201601";>
<operations>
<operator>ADD
</operator>
<operand
xsi:type="BiddableAdGroupCriterion">
<adGroupId>29068739164
</adGroupId>
<criterion
xsi:type="CriterionUserList">
<userListId>11461606624
</userListId>
<userListName>AudienceForSync31461606624
</userListName>
<userListMembershipStatus>OPEN
</userListMembershipStatus>
</criterion>
<bidModifier>0.1
</bidModifier>
</operand>
</operations>
<operations>
<operator>ADD
</operator>
<operand
xsi:type="BiddableAdGroupCriterion">
<adGroupId>29068739164
</adGroupId>
<criterion
xsi:type="CriterionUserList">
<userListId>21461606624
</userListId>
<userListName>AudienceForSync41461606624
</userListName>
<userListMembershipStatus>OPEN
</userListMembershipStatus>
</criterion>
<bidModifier>10
</bidModifier>
</operand>
</operations>
</mutate>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
*SOAP Response:*
<?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/v201601";>
<requestId>00053152cfa7db880ac11896a10d4cab
</requestId>
<serviceName>AdGroupCriterionService
</serviceName>
<methodName>mutate
</methodName>
<operations>2
</operations>
<responseTime>74
</responseTime>
</ResponseHeader>
</soap:Header>
<soap:Body>
<soap:Fault>
<faultcode>soap:Server
</faultcode>
<faultstring>[EntityNotFound.INVALID_ID @
operations[0].operand.criterion.userListId; trigger:11461606624,
EntityNotFound.INVALID_ID @ operations[1].operand.criterion.userListId;
trigger:21461606624]
</faultstring>
<detail>
<ApiExceptionFault
xmlns="https://adwords.google.com/api/adwords/cm/v201601";>
<message>[EntityNotFound.INVALID_ID @
operations[0].operand.criterion.userListId; trigger:11461606624,
EntityNotFound.INVALID_ID @ operations[1].operand.criterion.userListId;
trigger:21461606624]
</message>
<ApplicationException.Type>ApiException
</ApplicationException.Type>
<errors
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:type="EntityNotFound">
<fieldPath>operations[0].operand.criterion.userListId
</fieldPath>
<trigger>11461606624
</trigger>
<errorString>EntityNotFound.INVALID_ID
</errorString>
<ApiError.Type>EntityNotFound
</ApiError.Type>
<reason>INVALID_ID
</reason>
</errors>
<errors
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:type="EntityNotFound">
<fieldPath>operations[1].operand.criterion.userListId
</fieldPath>
<trigger>21461606624
</trigger>
<errorString>EntityNotFound.INVALID_ID
</errorString>
<ApiError.Type>EntityNotFound
</ApiError.Type>
<reason>INVALID_ID
</reason>
</errors>
</ApiExceptionFault>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
The error appears to be related to the CriterionUserList not *already*
existing. Since this is an ADD operation I am confused as to why that
fails, and why it only started failing recently.
Thanks.
Hunter.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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
---
You received this message because you are subscribed to the Google Groups
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/2f9ca45b-3b3d-428b-abfb-5754dda9e668%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
