incomplete fieldPath in the PolicyFindingError

[Hendrik Boon]

Since the v201806 release we experience PolicyFindingError in some cases (instead of PolicyViolationError) when creating Expanded Text Ads.

The problem with the PolicyFindingError is that we can not find which field caused an error in the fieldPath. For example: when creating an ad with '!!' in headline1 the fieldPath in the PolicyFindingError is 'operations[0].operand.ad'.

When we create for example an ad with ':' in path2 we get an StringFormatError with fieldPath: 'operations[0].operand.ad.path2'

Could it be fixed that the PolicyFindingError also gives the information which field of the Ad triggered the error? Or is there a workaround for this problem?

Regards,

Hendrik Boon

[Milind Sankeshware (AdWords API Team)]

Hi Hendrik,

Looks like you have created the another thread for the same issue. Could you please continue the discussion on that thread to avoid the duplication?

Thanks,
Milind, AdWords API Team