To follow up on this, 
As mentioned in the blog post, the recommended way to retrieve large set of 
result is 
- narrow the query as much as possible with predicates 
or 
- Use Adhoc reports 

If there is any fields missing in adhoc reports, we're going to make it 
available in adhoc reports. 
(e.g. ad params) 

Before it's available in adhoc reports, please use predicates to narrow 
down results.

Best,
- Takeshi, AdWords API Team

On Sunday, September 8, 2013 2:06:11 PM UTC+9, Takeshi Hagikura wrote:
>
> Hi Dorian,
>
> This was an expected behavior. 
> In the first place, AdWords API does not allow you to retrieve data whose 
> start index is past 50000 (the maximum number increased to 1000000 though).
> Please see 
> http://googleadsdeveloper.blogspot.jp/2012/02/adwords-api-retrieving-large-result.html.
>
> So if the size of the result is large, please use adhoc reports or try to 
> narrow the query with predicates. 
>
> Best,
> - Takeshi, AdWords API Team
>
> On Friday, September 6, 2013 3:50:11 AM UTC+9, Dorian Kind wrote:
>>
>> Hi Takeshi,
>>
>> thanks for your answer, however I am not sure I understand your 
>> suggestion. Removing paging.startIndex works fine, but how are we then 
>> supposed to fetch results beyond the maximum value of paging.numberResults? 
>> In my test, I received a SizeLimitError.RESPONSE_SIZE_LIMIT_EXCEEDED 
>> error when raising numberResults beyond approximately 10'000.
>>
>> Cheers,
>> Dorian
>>
>> On Thursday, September 5, 2013 8:42:19 PM UTC+2, Takeshi Hagikura 
>> (AdWords API Team) wrote:
>>>
>>> Hi everyone, 
>>>
>>> Thanks for sharing requestIds. 
>>> Looks like the limit for paging.startIndex was changed. 
>>>
>>> Can you please try removing startIndex to see if it works as a 
>>> workaround?
>>>
>>> Best,
>>> - Takeshi, 
>>>
>>> On Thursday, September 5, 2013 12:20:05 PM UTC+9, mm wrote:
>>>>
>>>> FWIW, we are also seeing this error - can supply additional Request 
>>>> ID's if that is useful
>>>>
>>>> Thanks -
>>>> mm
>>>>
>>>> On Tuesday, September 3, 2013 9:35:16 AM UTC-5, [email protected]:
>>>>>
>>>>> Hi Takeshi,
>>>>>
>>>>> We also seem to be experiencing this issue. 
>>>>> We have a client account that, according to the AdParamPage objects we 
>>>>> get from the adparamservice, contains 
>>>>> 402856 ad params. After succesfully retrieving a number of pages we 
>>>>> get: [SelectorError.START_INDEX_IS_TOO_HIGH @ ; trigger:'190000']
>>>>>
>>>>>
>>>>> Request ID: 0004e57b8f9aa3680ae5500a0000660d
>>>>>
>>>>>
>>>>> Thank you for looking into this matter.
>>>>>
>>>>>
>>>>> Kind regards,
>>>>>
>>>>> Jaap-Jan Frans 
>>>>> bGenius
>>>>>
>>>>>
>>>>>
>>>>> 0004e57b6dc1b4c00ae599cb000065dd
>>>>>
>>>>> For example we have an account that has 402856 ad params, and we get 
>>>>> the start index too high message when we reach start index 
>>>>> Example request ID: 
>>>>>
>>>>> Op maandag 2 september 2013 14:39:59 UTC+2 schreef Takeshi Hagikura 
>>>>> (AdWords API Team):
>>>>>>
>>>>>> Hi Dorlan,
>>>>>>
>>>>>> Thanks for the report. 
>>>>>> Could you please tell us the example requestId (It's included in the 
>>>>>> soap response)? 
>>>>>> I'll look into that.
>>>>>>
>>>>>> Best,
>>>>>> - Takeshi, AdWords API Team
>>>>>>
>>>>>> On Monday, September 2, 2013 4:46:57 PM UTC+9, Dorian Kind wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> as this issue is affecting us quite heavily, I'm bumping this 
>>>>>>> thread. If any request IDs or SOAP logs would be of help, I'll gladly 
>>>>>>> provide them.
>>>>>>>
>>>>>>> Many thanks and best regards,
>>>>>>> Dorian
>>>>>>>
>>>>>>> On Thursday, August 29, 2013 5:30:06 PM UTC+2, Dorian Kind wrote:
>>>>>>>>
>>>>>>>> Hi all,
>>>>>>>> since yesterday, we started to see 
>>>>>>>> SelectorError.START_INDEX_IS_TOO_HIGH 
>>>>>>>> errors when fetching all AdParams for a given campaign, even though 
>>>>>>>> there 
>>>>>>>> are more AdParams existing. These errors usually start appearing at an 
>>>>>>>> offset of around 120000. The campaign in question currently has 148124 
>>>>>>>> AdParams set as indicated by the "totalNumEntries" of the returned 
>>>>>>>> pages that are working; entries beyond a specifc offset however just 
>>>>>>>> throw 
>>>>>>>> a START_INDEX_IS_TOO_HIGH error.
>>>>>>>> I'd be grateful for any hints as we have currently no way at all to 
>>>>>>>> retrieve a complete list of AdParams for that specific campaign.
>>>>>>>> Best regards,
>>>>>>>> Dorian
>>>>>>>>
>>>>>>>>
>>>>>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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

--- 
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].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to