Cheers I am doing that, but as you say a little excessive and surplus if
the api returned the object type,.,...
John
On Monday, 18 February 2013 13:00:46 UTC, ig...@blueclaw.co.uk wrote:
>
> I usually store operation dump in a data store and check *fieldPath *for
> index of the operation that f
I usually store operation dump in a data store and check *fieldPath *for
index of the operation that failed to find exact operation, although it
might seem excessive it does the trick.
Hope that helps.
On Monday, 18 February 2013 12:12:06 UTC, John Lister wrote:
>
> I do group all operations as
I do group all operations as recommended, I just try to send them in as few
jobs as possible. For example I may update 50 groups, 10 ads and 200
keywords in one go which is fired off as 1 job rather than 3. All elements
within the job are ordered as recommended in the linked document.
Thanks
J
Hello John,
Errors are often shared between services and having separate set for each
one would not be efficient. Please also note it is recommended to group
operations per type and target as described here:
https://developers.google.com/adwords/api/docs/guides/bestpractices#group_operation
HI thanks for replying, I've just realised that I wasn't as clear as I
could be. I am using the fields you mention to track the error, but the
fieldPath only gives me the item number that caused the problem. My issue
is that I'm submitting different objects in the same job (for efficiency
reaso
Hello John,
Are you using the MutateJobService? Each error should have 'reason',
'trigger' and 'fieldPath' fields that should describe the issue.
-Danial, AdWords API Team.
On Saturday, February 16, 2013 12:58:24 AM UTC+4, John Lister wrote:
>
> Hi, when I do a BulkJob I can see in the resu
Hi, when I do a BulkJob I can see in the results the type of object
operated on by querying the operand object, however when an error occurs I
can't seem to find a way to get the same information. Although the error is
usually a subclass of error that indicates sometimes the object in question
