Re: Unexpected ApiError.fieldPathElements result (Perl v201702)

Hi Christian, Thanks for the update. If you encounter a separate issue please open a new topic and we'll be happy to help. Cheers, Josh, AdWords API Team On Thursday, May 18, 2017 at 4:12:47 AM UTC-4, Christian wrote: > > Hi Josh, > > the other issue I mentioned appears to be a problem on our s

Re: Unexpected ApiError.fieldPathElements result (Perl v201702)

Hi Josh, the other issue I mentioned appears to be a problem on our side. So everything is fine on the API side. Best, Christian On Thursday, May 18, 2017 at 1:30:48 AM UTC+2, Josh Radcliff (AdWords API Team) wrote: > > Hi Phil, > > Thanks for confirming. Glad to hear things are behaving as ex

Re: Unexpected ApiError.fieldPathElements result (Perl v201702)

Hi Phil, Thanks for confirming. Glad to hear things are behaving as expected now. Cheers, Josh, AdWords API Team On Wednesday, May 17, 2017 at 1:47:17 PM UTC-4, Phillip Pegelow wrote: > > Josh, > > The tests that were previously failing are now passing and the > fieldpathelements of the error o

Re: Unexpected ApiError.fieldPathElements result (Perl v201702)

Josh, The tests that were previously failing are now passing and the fieldpathelements of the error objects are as we would expect. Thank you very much for your help, Phil On Tuesday, May 16, 2017 at 7:54:02 PM UTC-4, Josh Radcliff (AdWords API Team) wrote: > > Hi Christian, > > The fix for th

Re: Unexpected ApiError.fieldPathElements result (Perl v201702)

Hi Josh, thanks for the fix. The index numbers in fieldPath and fieldPathElements now look correct. The other issue ("ad group and criterion ID mentioned in *trigger* do not match the IDs of the original operations in the batch job at that index") still exists. But let me first check if this p

Re: Unexpected ApiError.fieldPathElements result (Perl v201702)

Hi Christian, The fix for this issue is now in place. Could you retry your batch jobs and let me know if you still see either issue? Thanks, Josh, AdWords API Team On Monday, May 15, 2017 at 8:07:46 PM UTC-4, Josh Radcliff (AdWords API Team) wrote: > > Hi Christian, > > Thanks for sending over

Re: Unexpected ApiError.fieldPathElements result (Perl v201702)

Hi Christian, Thanks for sending over the batch job ID. After taking a closer look at the operations and results for that job, I suspect that this *is* related to the same issue you raised earlier after all. I suggest we wait for the fix for that one (should be soon), then see if that resolves

Re: Unexpected ApiError.fieldPathElements result (Perl v201702)

Hi Christian, That looks like it may be a separate issue. Could you send me the batch job ID for the job you mentioned below so I can confirm? Thanks, Josh, AdWords API Team On Saturday, May 13, 2017 at 4:52:54 PM UTC-4, Christian wrote: > > Hi, > > we also started to see strange error response

Re: Unexpected ApiError.fieldPathElements result (Perl v201702)

Hi, we also started to see strange error responses in the BatchJobService. We use the googleads Python library. Here is an example error: { u'errorString': u'EntityNotFound.INVALID_ID', u'fieldPath': u'operations[18342].operand.criterion', u'reason': u'INVALID_ID', u'trigger': u'No exist

Re: Unexpected ApiError.fieldPathElements result (Perl v201702)

Hi Phil, We're actively working on a fix for this. I'll update this post as soon as it's in place. Thanks, Josh, AdWords API Team On Monday, May 8, 2017 at 10:14:52 AM UTC-4, Phillip Pegelow wrote: > > Any update on this? > > Thanks, > Phil > > On Thursday, May 4, 2017 at 3:53:58 PM UTC-4, Josh

Re: Unexpected ApiError.fieldPathElements result (Perl v201702)

Any update on this? Thanks, Phil On Thursday, May 4, 2017 at 3:53:58 PM UTC-4, Josh Radcliff (AdWords API Team) wrote: > > Hi, > > Thanks for confirming. I tried this out as well and confirmed that there > is an extra *fieldPathElement* in errors from *BatchJobService*, but not > in errors fro

Re: Unexpected ApiError.fieldPathElements result (Perl v201702)

Hi, Thanks for confirming. I tried this out as well and confirmed that there is an extra *fieldPathElement* in errors from *BatchJobService*, but not 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 th

Re: Unexpected ApiError.fieldPathElements result (Perl v201702)

Thank you for the reply, Josh, Yes, this does appear to be unique to the BatchJobService. I have not experienced this behavior elsewhere. On Wednesday, May 3, 2017 at 5:50:18 PM UTC-4, Josh Radcliff (AdWords API Team) wrote: > > Hi, > > Are you only seeing this issue with specific services, or

Re: Unexpected ApiError.fieldPathElements result (Perl v201702)

Hi, Are you only seeing this issue with specific services, or only when using BatchJobService ? I ask because I just ran a few tests with AdGroupCriterionService

Unexpected ApiError.fieldPathElements result (Perl v201702)

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