INVALID_PROXIMITY_ADDRESS occurs for valid data episodically

[Dmitry Karpuk]

I use the version 201710 and about a week ago I started getting errors CriterionError.INVALID_PROXIMITY_ADDRESS. I have some address and sometimes it works for it correctly, and sometimes I get this error. What is going on? It does seem as bug on your side.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

    <soap:Header>

        <ResponseHeader xmlns="https://adwords.google.com/api/adwords/cm/v201710">

            <requestId>00056b996898a9c80a3713077f03c18b</requestId>

            <serviceName>CampaignCriterionService</serviceName>

            <methodName>mutate</methodName>

            <operations>2</operations>

            <responseTime>113</responseTime>

        </ResponseHeader>

    </soap:Header>

    <soap:Body>

        <soap:Fault>

            <faultcode>soap:Client</faultcode>

            <faultstring>[CriterionError.INVALID_PROXIMITY_ADDRESS @ operations[0].operand.criterion.address, CriterionError.INVALID_PROXIMITY_ADDRESS @ operations[1].operand.criterion.address]</faultstring>

            <detail>

                <ApiExceptionFault xmlns="https://adwords.google.com/api/adwords/cm/v201710">

                    <message>[CriterionError.INVALID_PROXIMITY_ADDRESS @ operations[0].operand.criterion.address, CriterionError.INVALID_PROXIMITY_ADDRESS @ operations[1].operand.criterion.address]</message>

                    <ApplicationException.Type>ApiException</ApplicationException.Type>

                    <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="CriterionError">

                        <fieldPath>operations[0].operand.criterion.address</fieldPath>

                        <fieldPathElements>

                            <field>operations</field>

                            <index>0</index>

                        </fieldPathElements>

                        <fieldPathElements>

                            <field>operand</field>

                        </fieldPathElements>

                        <fieldPathElements>

                            <field>criterion</field>

                        </fieldPathElements>

                        <fieldPathElements>

                            <field>address</field>

                        </fieldPathElements>

                        <trigger/>

                        <errorString>CriterionError.INVALID_PROXIMITY_ADDRESS</errorString>

                        <ApiError.Type>CriterionError</ApiError.Type>

                        <reason>INVALID_PROXIMITY_ADDRESS</reason>

                    </errors>

                    <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="CriterionError">

                        <fieldPath>operations[1].operand.criterion.address</fieldPath>

                        <fieldPathElements>

                            <field>operations</field>

                            <index>1</index>

                        </fieldPathElements>

                        <fieldPathElements>

                            <field>operand</field>

                        </fieldPathElements>

                        <fieldPathElements>

                            <field>criterion</field>

                        </fieldPathElements>

                        <fieldPathElements>

                            <field>address</field>

                        </fieldPathElements>

                        <trigger/>

                        <errorString>CriterionError.INVALID_PROXIMITY_ADDRESS</errorString>

                        <ApiError.Type>CriterionError</ApiError.Type>

                        <reason>INVALID_PROXIMITY_ADDRESS</reason>

                    </errors>

                </ApiExceptionFault>

            </detail>

        </soap:Fault>

    </soap:Body>

</soap:Envelope>

[Dhanya Sundararaju (AdWords API Team)]

Hi Dmitry,

Our team is aware of this issue and is currently looking into it. I will keep you posted on the updates.

Regards,
Dhanya, AdWords API Team

[Bridgette Meagher]

Hi Dhanya, 

We are facing the same issue as well. Is there any update?

[Dhanya Sundararaju (AdWords API Team)]

Hi Bridgette,

Thank you for letting us know. This issue is being worked upon. At this point, there is no ETA but I will keep you posted on the updates. 

[Dhanya Sundararaju (AdWords API Team)]

Hi all,

This issue has been fixed. Please test at your end and reply back on this thread if you still have issues.