Thanks for getting to the bottom of this.
Not something we had anticipated. We have scheduled the release of a
workaround.
Thanks
On Saturday, March 3, 2012 8:30:23 AM UTC+11, Kevin Winter wrote:
> Hi,
> Our production monitoring has been seeing an increased amount of traffic
> associated
Hi,
Our production monitoring has been seeing an increased amount of traffic
associated with your developer token. We believe it's due to the issue
you've reported here. Until we can fix the issue, we'd like to request
that you alter your paging algorithm to increment the startIndex by the
Hi,
I was able to reproduce this in my account. I believe that the cause is
the mobile operating system versions that have been specified in the
Campaign Settings for this campaign. The API doesn't support these
settings yet, so when returning CampaignCriteria they get filtered out of
the r
Hi Kevin,
This is in the production environment, in a live client account.
This is the only instance we are aware of which has this behaviour. Quite
possibly the only instance where it occurs.
But it happens consistently (every time) for this campaign.
Thanks
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=
Hi,
Is this a request in the sandbox? The sandbox is (unfortunately)
occasionally flaky and may have bad data (i.e. the AdGroup may not have
been created successfully).
Do you see this with other campaigns or just this one? Can you recreate
this behavior in a different campaign?
- Kevin Wi
Hi,
We have a SOAP request for campaign criterion.
We reuest with a page size of 5000, the response comes back with 45
criterion, but says there are 47 in total.
So our paging logic then makes a second request for 5000 items with a
startIndex of 45. The response comes back with 0 records, but still
