Hi Josh, 

No we used a different UserList each time, and the Id using for that 
UserList was based on the current time the test was run i.e. UserList<unix 
timestamp>. The workflow for this test was as follows :

1. Create a campaign
2. Create an adgroup
3. Create a CriterionUserList object from the Perl client library
4. Create a BiddableAdGroupCriterion object from the Perl client library 
pointing to the CriterionUserList from (3)
5. Create an AdGroupCriterionOperation object from the Perl client library 
with an operand of the AdGroupCriterion from (4) and operator of 'ADD'
6. Call the mutate method of the AdGroupCriterionService passing the 
operation from (5)

Thanks, 
Hunter.

On Tuesday, April 26, 2016 at 9:09:50 AM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Hunter,
>
> I'm not aware of any recent changes in behavior. Could you provide more 
> details on your test set up? One possibility is that the *UserList* you 
> were using for your tests was deleted on or around 4/20. Do you use an 
> existing *UserList* in your tests, or recreate one each time the test 
> runs?
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, April 26, 2016 at 9:06:20 AM UTC-4, Hunter wrote:
>>
>> Hi Josh, 
>>
>> So this is definitely not a recent change? Our logs indicate this 
>> behavior started occurring on 2016-04-20, previously this test had been 
>> running for ~7 months without issue. 
>>
>> Thanks.
>> Hunter.
>>
>> On Monday, April 25, 2016 at 4:44:30 PM UTC-4, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Hunter,
>>>
>>> When constructing your *CriterionUserList*, the userListId 
>>> <https://developers.google.com/adwords/api/docs/reference/v201603/AdGroupCriterionService.CriterionUserList#userlistid>
>>>  must 
>>> refer to an existing UserList 
>>> <https://developers.google.com/adwords/api/docs/reference/v201603/AdwordsUserListService.UserList#id>.
>>>  
>>> You can verify that the *userListId* specified is a valid ID by 
>>> checking the results from AdwordsUserListService.get 
>>> <https://developers.google.com/adwords/api/docs/reference/v201603/AdwordsUserListService#get>
>>> .
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, April 25, 2016 at 2:30:02 PM UTC-4, Hunter wrote:
>>>>
>>>> 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 [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
--- 
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 [email protected].
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/9af17ba3-596a-439b-aa64-a0cae86e0de7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • Issue creating Cr... Hunter
    • Re: Issue cr... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
      • Re: Issu... Hunter
        • Re: ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
          • ... Hunter
            • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
              • ... Hunter
                • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
                • ... Hunter

Reply via email to