Re: INVALID_PROXIMITY_ADDRESS occurs for valid data episodically

[Josh Radcliff (AdWords API Team)]

Hi,

Do you happen to have request IDs from a response for a request that succeeded and a request that failed?

Thanks,

Josh, AdWords API Team

On Wednesday, March 4, 2015 at 1:57:47 AM UTC-5, Dzmitry Zahusta wrote:

Hi!

While performing the following code INVALID_PROXIMITY_ADDRESS occurs episodically

        Address address = new Address();

        address.setCityName("Johnson City");

        address.setCountryCode("Tennessee");

        address.setProvinceName("US");

        Proximity proximity = new Proximity();

        proximity.setAddress(address);

        proximity.setRadiusDistanceUnits(ProximityDistanceUnits.MILES);

        proximity.setRadiusInUnits(30.0);

        CampaignCriterion campaignCriterion = new CampaignCriterion();

        campaignCriterion.setCampaignId(campaignId);

        campaignCriterion.setCriterion(proximity);

        CampaignCriterionOperation operation = new CampaignCriterionOperation();

        operation.setOperand(campaignCriterion);

        operation.setOperator(Operator.ADD);

        campaignCriterionService.mutate(new CampaignCriterionOperation[] { operation });

After repeating this code with no changes proximity is added with no issue. The proper address data may vary. 

What is going on? It does seem as bug on your side.

[Josh Radcliff (AdWords API Team)]

Hi,

I just noticed that in your code snippet, you are setting the provinceName to US and the countryCode to Tennessee, which is invalid. You should be setting the provinceName to Tennessee and the countryCode to US.

Thanks,

Josh, AdWords API Team

On Friday, March 6, 2015 at 1:33:08 PM UTC-5, Dzmitry Zahusta wrote:

Unfortunately I can provide only Ids of problematic campaigns:

'276257069' ('US Georgia Warner Robins')

'264091949' ('US California Hayward')

'243337469' ('US Tennessee Alcoa')

пятница, 6 марта 2015 г., 1:35:47 UTC+3 пользователь Josh Radcliff (AdWords API Team) написал:

[Josh Radcliff (AdWords API Team)]

Hi,

I've tried reproducing this behavior multiple times but in all cases the address you provided is accepted.

One thing you may want to do is use GeoLocationService to first validate your address. This will give you back a GeoLocation if the address is valid, whose geoPoint you can then use in your Proximity object instead of the address. If the address is invalid, it will give you back an InvalidGeoLocation object.

If you see this inconsistency again, please capture the request IDs of the failed requests and send them over.

Cheers,

Josh, AdWords API Team

On Monday, March 9, 2015 at 11:38:25 AM UTC-4, Dzmitry Zahusta wrote:

Yep, you are right but it's just typo in my example. In reality all is set in a right way.

понедельник, 9 марта 2015 г., 18:28:52 UTC+3 пользователь Josh Radcliff (AdWords API Team) написал:

[Josh Radcliff (AdWords API Team)]

Hi,

At the moment, you would have to get them from your SOAP logs. We have an open issue for improving the capture of request IDs in the library.

Thanks,

Josh, AdWords API Team

On Tuesday, March 10, 2015 at 9:43:11 AM UTC-4, Dzmitry Zahusta wrote:

Hi,

I've already changed my logic to what you mentioned (set geoPoint together with Address object). 

but can you please clarify how I can get request IDs in Java code?

вторник, 10 марта 2015 г., 16:10:33 UTC+3 пользователь Josh Radcliff (AdWords API Team) написал:

[Josh Radcliff (AdWords API Team)]

Hi,

Thanks for sending over the new addresses where you saw this issue. I'll see if I can track down more information on the requests that failed and get back to you.

Cheers,

Josh, AdWords API Team

On Tuesday, March 17, 2015 at 3:08:08 AM UTC-4, Dzmitry Zahusta wrote:

The problem still persist. I reworked the code to get GeoPoint byGeoLocationService 

        GeoLocationSelector selector = new GeoLocationSelector();
        selector.setAddresses(addresses.toArray(new Address[0]));
        GeoLocation[] geoLocationResult = geoLocationService.get(selector);

And I see in logs that for the following addresses:

• Augusta,Georgia,United States
  
• 30909,Georgia,United States
  

The code returns InvalidGeoLocation with geoPoint = null.

After repeating code a bit later with the same data all is working in a right way

As I can not provide you request Ids because I'm submitting data by Java API which information can help you to investigate the issue? 

вторник, 10 марта 2015 г., 18:14:33 UTC+3 пользователь Josh Radcliff (AdWords API Team) написал:

[Josh Radcliff (AdWords API Team)]

Hi,

Thanks for sending over more examples. This time I was able to find the request IDs for your requests.

I reported this issue to the engineering team and provided your request IDs. I'll post back here as soon as I have an update.

Thanks,

Josh, AdWords API Team

On Wednesday, March 25, 2015 at 2:44:04 AM UTC-4, Dzmitry Zahusta wrote:

Hi,

The same issue again with:

• 98801,Washington,United States
  
• San Leandro,California,United States
  
• Post Falls,Idaho,United States
  
• Knoxville,Tennessee,United States
  

As always - if you resubmit these addresses again later, it will work with no errors.

Let's start investigating it...

среда, 18 марта 2015 г., 0:40:37 UTC+3 пользователь Josh Radcliff (AdWords API Team) написал:

[Josh Radcliff (AdWords API Team)]

Hi,

Thanks for sending over more examples. I've passed these along to the team that's looking into this issue.

Cheers,

Josh, AdWords API Team

On Tuesday, April 7, 2015 at 2:02:57 AM UTC-4, Dzmitry Zahusta wrote:

Hi,

This happen again for 

'Santa Rosa,California,United States'

'Blue Ridge,Georgia,United States'

'Villa Rica,Georgia,United States'

'Alcoa,Tennessee,United States'

среда, 25 марта 2015 г., 19:01:52 UTC+3 пользователь Josh Radcliff (AdWords API Team) написал:

[Josh Radcliff (AdWords API Team)]

Hi Dzmitry,

We've identified the source of this problem, but I don't have an ETA yet for when this will be resolved. I'll let you know when I have more information, but in the meantime I'd recommend you continue your approach of retrying failed requests.

Thanks,

Josh, AdWords API Team

On Tuesday, May 5, 2015 at 7:49:51 AM UTC-4, Dzmitry Zahusta wrote:

Hi Josh,

Have you been able to repeat and resolve the issue? The problem is still continued on my side. Can send a bunch of addresses if necessary.

четверг, 9 апреля 2015 г., 23:30:15 UTC+3 пользователь Josh Radcliff (AdWords API Team) написал:

[Josh Radcliff (AdWords API Team)]

Hi Dzmitry,

I've asked for an update from the team working on this issue. You mentioned a specific time period when this happened at a high rate. Could you send me the dates and times for that window, including the time zone?

Thanks,

Josh, AdWords API Team

On Wednesday, July 29, 2015 at 5:54:26 PM UTC+9, Dzmitry Zahusta wrote:

Hi Josh,

Last time this kind of error starts occuring too often and the period when it continue happening too long (2+ hours) so even my code that re-submit failed request are unsuccessful. My business owneres is becoming nervous as it's necessary to handle failed campaigns manually.

Please suggest something to sort out this issue.

вторник, 5 мая 2015 г., 16:32:24 UTC+3 пользователь Josh Radcliff (AdWords API Team) написал: