Hi Tozor,
I agree that more documentation is needed around locking, and I'll see
what I can do about improving that. For large enough jobs, I can see
how retries may not be enough to avoid errors altogether, but with
enough retries you should be able to achieve a high success rate. I
think it m
Thanks for the detailed response. I have tried retrying with even up
to a 5 second delay between failures but I still see an error.
However given your explanation of campaign level locking, I think it
is going to be problematic to update the URL of multiple criterias via
a single call to updateC
Hi Tozor,
Thank you for taking the time to get me a RequestId, as it helps me
immensely when trying to track down an issue. Including this
information in the fault text could be a good idea, and I will bring
this up with the core development team.
I looked into the problem that you encountered
Ok I figured out how to get the request id in my java v13 environment
via the AdwordsServiceLogger.log() method. The request id of the
failing request was 273216e94875b516cd2b478a4b9595f1.
I would like to reiterate that it would be really cool if the request
id was returned in the error message.
How do I get at the request ID? Is there some sort of logging I am
supposed to enable? Assuming that your answer is yes, can I make a
comment that it would be nice if the Adwords server dumped out the
request id in the error message so that I don't have to recompile code
and then install it into
Hi Tim,
I will look into the logs and see if I can get more information about
these errors you are running up against. Can you please send me the
Request ID of an updateCriteria request that generated the error?
Thanks,
- Eric Koleda, AdWords API Team
On Aug 19, 9:29 am, tozor wrote:
> I seem
