Hello!
We are migrating to the new Google Ads API. We are using OfflineUserDataJob service. We have the following workflow:
1. Create a job: https://developers.google.com/google-ads/api/rest/reference/rest/v9/customers.offlineUserDataJobs/create
2. Add Operations to the created job: https://developers.google.com/google-ads/api/rest/reference/rest/v9/customers.offlineUserDataJobs/addOperations.
We are adding 10.000 operations as recommended https://developers.google.cn/google-ads/api/docs/conversions/upload-store-sales-transactions?authuser=0&hl=id#tips.
3. Run the job: https://developers.google.com/google-ads/api/rest/reference/rest/v9/customers.offlineUserDataJobs/run
We receive CONCURRENT_MODIFICATION error since we process these tasks in parallel and multiple processes are trying to modify the same user list simultaneously.
Reading the response https://groups.google.com/g/adwords-api/c/gdYUwIhh9eU/m/k8qaO0HSDgAJ it seemed to me we need to wait until one job is finished and only after that we should create a new job.
But I was able to create and run two jobs containing “create” operations and one job containing “remove” operations and didn’t receive any errors. I checked that my list had multiple jobs with “RUNNING” status.
My question is: Is it acceptable to create and run job 1, after some time create and run job 2 when the job 1 is still in “RUNNING” status? Is it acceptable to have multiple jobs in the “RUNNING” status for the same user list?
Could you, please, help me with my question?
|
||||||
Hi Alexandra,
It's not possible for our team to increase rate limits. Also, there isn't a specific QPS rate limit associated with the UserDataService. A discussion about dealing with rate limits can be found on this page.
Let us know if you have any further clarification.
Regards,
|
||||||