Re: DatabaseError.CONCURRENT_MODIFICATION error

Hello Qian, As a suggestion to avoid such errors in a multi threaded environment, I would like to share some best practices from this handy guide. One recommendation in that guide includes : "When you retry requests, use an exponential backoff policy. For example, if you first pause 5 seconds b

Re: DatabaseError.CONCURRENT_MODIFICATION error

Hi Nikisha, For one user list, we will add millions of users, so currently we chunk them into several requests, each request will contain 1000 user mutation, then we send these requests concurrently. If the concurrent modification error is happend on user list level, it means we can't send th

Re: DatabaseError.CONCURRENT_MODIFICATION error

Hello Qian, The entity in this scenario will refer to the user list that you are trying to update via API for mutating members of the user list. The concurrent modification error indicates that two or more processes are trying to update the same user list at same instance of time. It might also

Re: DatabaseError.CONCURRENT_MODIFICATION error

Hi Nikisha, I checked change history, looks like only one script is sending request. However, the history are quite general, it only says: "Remarketing list changed", "Members are uploaded to add to this list". Could you tell more details about that for this mutate member api, what's the defin

RE: DatabaseError.CONCURRENT_MODIFICATION error

Hello Qian, Thank you for reaching out. The CONCURRENT_MODIFICATION error is observed when multiple processes are trying to make changes to a single entity at once. Could you please check the Change History in the Google Ads interface to verify if there were no other changes being made to the a

RE: DatabaseError.CONCURRENT_MODIFICATION

Hello Aaron, Your idea of going through the Change History for your account was an excellent one. That was my first place to look as well. What I found during that time for that account was that there are Google Ads scripts running in that account at the same time. Only a minute or so before yo

RE: DatabaseError.CONCURRENT_MODIFICATION

Hi Aaron, Thank you for providing a detailed description about the issue you encountered. So I can further investigate, could you also provide the complete SOAP request and response logs that were generated when the error occurred? You may send your reply via the *Reply privately to author* opt

RE: DatabaseError.CONCURRENT_MODIFICATION

Hello Aishwarya, I have sent the below response to you email privately, If you have any further questions please let me know. - The sizeRange field must be related to the disp

Re: DatabaseError.CONCURRENT_MODIFICATION

Hi Team, Could anyone update on the below items? Thanks On Saturday, April 13, 2019 at 11:36:06 PM UTC+5:30, ci.wb...@gmail.com wrote: > > Hi Sai Teja, > > Thank you for the responses. One follow question regarding point 1. > I have attached the screenshot for your reference as we

Re: DatabaseError.CONCURRENT_MODIFICATION

Hi Sai Teja, Thank you for the responses. One follow question regarding point 1. I have attached the screenshot for your reference as well. SizeRangeForSearch field is showing almost acceptable number of users I uploaded from my end and almost equal to the matched % of users displayed in

RE: DatabaseError.CONCURRENT_MODIFICATION

Hello Aishwarya, Please find the response below inline: 1. is there any way to identify how many userids have been uploaded altogether into the userlist before Google does Hashmapping with their list? *You could use sizeRange

Re: DatabaseError.CONCURRENT_MODIFICATION

Thank you for the reply. Now I am stuck up with another issue. When I am splitting up into multiple groups and uploading it into the same userlist, is there any way to identify how many userids have been uploaded altogether into the userlist before Google does Hashmapping with their list? As of

Re: DatabaseError.CONCURRENT_MODIFICATION

Thank you for the reply. Now I am stuck up with another issue. When I am splitting up into multiple groups and uploading it into the same userlist, is there any way to identify how many userids have been uploaded altogether into the userlist before Google does Hashmapping with their list? As o

Re: DatabaseError.CONCURRENT_MODIFICATION

Thank you for the reply. Now I am stuck up with another issue. When I am splitting up into multiple groups and uploading it into the same userlist, is there any way to identify how many userids have been uploaded altogether into the userlist before Google does Hashmapping with their list? As of

RE: DatabaseError.CONCURRENT_MODIFICATION

Hello, You are right about the issue. The DatabaseError.CONCURRENT_MODIFICATION error occurs when multiple processes are trying to update the same entity at the same time. Adding delays would be

Re: DatabaseError.CONCURRENT_MODIFICATION

Hi Luis, Thanks for the reply. We tried to manually rerun the SOAP call this morning and then it didn't give any issues. Also running our full API implementation didn't give any problems this morning. So in short: the issue has been resolved by waiting a bit. The reason we still opened an issu

Re: DatabaseError.CONCURRENT_MODIFICATION

Hi Koen, The DatabaseError.CONCURRENT_MODIFICATION error that you encountered occurs due to multiple processes that are trying to update the same entity at the same time. It includes a user in

Re: DatabaseError.CONCURRENT_MODIFICATION on API version v201109

Hi Cristian, There are no restrictions on using multithreading with v201109. Nothing has changed on this aspect from v201101 to v201109. Danial suggested using MutateJobService because it takes care of issues like RateExceededError, Concurrent modification errors, etc. automatically. If you use

Re: DatabaseError.CONCURRENT_MODIFICATION on API version v201109

Hi Danial, thank you for your response. The post that you have linked to me is dated March 30 2011, so it refers to the v201101 version that is the version that allows me to use multithread. So I still not understand if there are (and if so what) new restrictions in the new v201109 version. T

Re: DatabaseError.CONCURRENT_MODIFICATION on API version v201109

Hello Cristian, The possible reasons for this error are described here: http://adwordsapi.blogspot.com/2011/03/concurrency-management-in-adwords-api.html In your particular case I recommend removing multi-threading and using MutateJobService

Re: DatabaseError.CONCURRENT_MODIFICATION on API version v201109

There were new restrictions related to the DatabaseError.CONCURRENT_MODIFICATION error between the two versions? Can you clarify what are the concurrent operations that can be done depending on the type of "scope"? Thank you -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on

Re: DatabaseError.CONCURRENT_MODIFICATION

Hello Surya, Please refer to the following article regarding this error: http://adwordsapi.blogspot.com/2011/03/concurrency-management-in-adwords-api.html Note the error can occur even if all your request are read only in some cases when internal background jobs could be running. -Danial,

Re: DatabaseError.CONCURRENT_MODIFICATION

Hi, We have a blog post that discusses DatabaseError.CONCURRENT_MODIFICATION error in detail. See http://adwordsapi.blogspot.com/2011/03/concurrency-management-in-adwords-api.html for more details. Cheers, Anash P. Oommen, AdWords API Advisor. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Re: DatabaseError.CONCURRENT_MODIFICATION on large keyword bids update query

Hello Rohit, This issue was recently described in our blog: http://adwordsapi.blogspot.com/2011/03/concurrency-management-in-adwords-api.html The best practice would be to have a retry mechanism with limited number of retries in place. Best regards, Danial Klimkin, AdWords API Team. --

Re: DatabaseError.CONCURRENT_MODIFICATION on large keyword bids update query

I have a retry in place (I believe the limit is 5 tries before giving up), and since the most recent api update we are seeing a significant increase in these failures (those that exceed our retry limit) - both for bid and url updates. Guys, is this a known issue? Suggestions for how we should stru

AdWords API Re: DatabaseError.CONCURRENT_MODIFICATION errors while updating ad group criteria (keywords)

Hi Chandra, Unfortunately there is no exact time that will prevent these types of errors of coming up from time to time. Your best bet is to: 1) Batch your updates together in fewer requests (http:// adwordsapi.blogspot.com/2010/03/discover-v2009-do-more-with- mutate.html) 2) Catch this type of

AdWords API Re: DatabaseError.CONCURRENT_MODIFICATION errors while updating ad group criteria (keywords)

Eric, Is there recommended wait between two same ad group or campaign? Would say a 5 sec delay suffice? Chandra On Mar 23, 12:12 pm, AdWords API Advisor wrote: > Hi, > > The most common causes of this error are: > > - Two threads working on the same account at the same time. > - Two updates to

AdWords API Re: DatabaseError.CONCURRENT_MODIFICATION errors while updating ad group criteria (keywords)

Hi, The most common causes of this error are: - Two threads working on the same account at the same time. - Two updates to the same ad group or campaign in short succession. In both cases the recommended reaction is to wait for a few seconds and try the request again. Best, - Eric Koleda, AdWor

AdWords API Re: DatabaseError.CONCURRENT_MODIFICATION errors while updating ad group criteria (keywords)

We used to get this when we tried running two mutate operations simultaneously on the same account ... could be any mix of services ... Campaign + AdGroup, Keyword + Keyword ... etc Pete On Mar 22, 12:58 pm, SEM wrote: > Hi, > > We are seeing this API error being thrown many times for some of ou

AdWords API Re: DatabaseError.CONCURRENT_MODIFICATION or which concurrent modifications are allowed?

Hi, For ads and keywords locking takes place at an ad group level. That is to say that you can't ADD/SET/REMOVE entities in the same ad group at the same time. It is recommended to catch these errors and retry your request, but you may also want to segment your updates so that different threads