Unfortunately we don't log the full SOAP response on failures (they are all
processed through the adwords perl library so they aren't typically of use
for debugging to us). On top of that, we implemented a work-around in
which we don't use the batch job service in order to not have this affect
Relates to https://groups.google.com/forum/#!topic/adwords-api/aTOWJMBFH1M
Parsing OperationAccessDenied error objects using the above perl library
(Google::Ads::Common::ErrorUtils::get_source_operation_index() )is
returning undef. It appears that the adwords library code expects calling
ad group and criterion ID mentioned in *trigger* do not match
>>>> the IDs of the original operations in the batch job at that index.
>>>>
>>>> Is this a related problem or an entirely different issue?
>>>>
>>>> Best,
>>>> Christian
>>
ot
> in errors from the synchronous services. I've asked the batch job team to
> investigate and will post back here as soon as I have an update from them.
>
> Thanks,
> Josh, AdWords API Team
>
> On Thursday, May 4, 2017 at 10:05:00 AM UTC-4, Phillip Pegelow wrote:
>>
&
> Josh, AdWords API Team
>
> On Wednesday, May 3, 2017 at 2:07:20 PM UTC-4, Phillip Pegelow wrote:
>>
>>
>> The newest Perl library, v4.13.0 v201702, introduced the
>> "fieldPathElements" field of ApiError. In testing prior to this
The newest Perl library, v4.13.0 v201702, introduced the
"fieldPathElements" field of ApiError. In testing prior to this upgrade, I
have noticed that the first fieldPathElements.operations index is always 0
and the second fieldPathElements.operations index is the expected index of
the failed
