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 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
>
> John
>
> On Monday, 18 February 2013 11:59:03 UTC, Danial Klimkin wrote:
>>
>> 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_operations
>>
>> So you may want to consider to send separate jobs for campaigns and 
>> criteria.
>>
>>
>> -Danial, AdWords API Team.
>>
>>
>> On Monday, February 18, 2013 3:35:33 PM UTC+4, John Lister wrote:
>>>
>>> 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 
>>> reasons) so position 1 may be a campaign, 2 maybe a keyword, etc It would 
>>> be nice if the error indicate the type of object as well so I could call 
>>> the right code to mark the error in our system. Its obviously not a 
>>> necessity as I'm storing the extra information when I submit the job
>>>
>>> Thanks
>>>
>>> John
>>>
>>> On Monday, 18 February 2013 11:28:37 UTC, Danial Klimkin wrote:
>>>>
>>>> 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 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 
>>>>> (for example CampaignError is obvious) most errors seem to be generic and 
>>>>> some object such as AdGroups don't have any distinct errors that I can 
>>>>> see. 
>>>>> The only option which seems excessive is to store the object type 
>>>>> separately in order to be able to deal with the error.
>>>>>
>>>>> Have I missed something?
>>>>>
>>>>> Thanks
>>>>>
>>>>> John
>>>>>
>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to