Hi Rainer, A key feature of the BulkMutateJobService is the ability to submit the job in multiple parts. Very large requests can be problematic, as server and client side limitations exist that can lead to timeouts, 502 errors, etc. For this reason we recommend breaking up large requests into multiple operation streams and/or parts. An example of using multiple parts can be found here:
http://adwordsapi.blogspot.com/2009/10/asynchronous-requests-with.html Unfortunately it isn't possible to cancel a running job. The running time of the job depends on the type of operations in the job, so the time you are seeing may be appropriate. Best, - Eric On Nov 23, 2:30 pm, rz <[email protected]> wrote: > > For which requests are you receiving the 502 errors? Are you > > splitting your requests into multiple operation streams and multiple > > parts? > > Our tests use only one OperationStream á 200-500 artefacts and one > Request per Job. Please note that these errors only seem to appear > when using the Sandbox-Environment. > > I am currently having a test running that uses a real account with 40 > AdGroups that have 10 AdGroupCriterions and 10 TextAds each. We have > not experienced Bad Gateway errors so far. I am currently waiting for > the last Job (400 TextAds in 4 OperationStreams in 4 RequestParts) to > finish (It's running for over 40minutes now ...). The previous job, > having 400 AdGroupCriterions, finished in under 5min. Is it normal to > wait this long for a (fairly normal) Job to finish ? > > Also: is there an operation/call that cancels a job ? > > Cheerfully waiting (and waiting and ... :), > rainer -- 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=.
