Hi Margaret,
We recently published a blog post that covers how concurrency management
works in the API:
http://adwordsapi.blogspot.com/2011/03/concurrency-management-in-adwords-api.html
In general large batch sizes are better, but it depends on what's in those
batches. One of our best prac
Fyi, we also regularly run cpc updates in batch sizes of 10 and are
seeing ConcurrentMod exceptions within that process pretty
consistently also.
On Apr 5, 12:49 pm, mm wrote:
> Latest update... I was running through a large number of keyword url
> updates (16k), uploading the changes in batches
Latest update... I was running through a large number of keyword url
updates (16k), uploading the changes in batches of 1000. When running
the updates this way, I was seeing a significant number of
ConcurrentModification exceptions, and no partial failures. I decided
to try a smaller batch size of
Hi Anash -
I just received this error for a couple of requests:
[04 Apr 2011 15:31:19,219 - DEBUG] email=
effectiveUser= service=AdGroupCriterionService method=mutate
operators={SET: 1000} responseTime=78581 operations=0 units=1
requestId=aa60417709fd3ec5cef99fc937494cc7 server=htt
Hi Margaret,
If you can share the response ids for such requests online, then that would
be most helpful.
Cheers,
Anash P. Oommen,
AdWords API Advisor.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://group
Hey guys -
The past week or so (seems to be since the latest release, but can't
say that definitively) we have seen a significant increase in the
number of ConcurrentModification exceptions thrown while updating
Keywords (in particular, when updating their destinationURLs). I've
already got a retry
