Re: UNEXPECTED_INTERNAL_API_ERROR at ConversionTrackerService.get()

2015-09-01 Thread Josh Radcliff (AdWords API Team)
Hi Zweitze, I don't think this points to any issues specifically with *ConversionTracker* since the failed *get* requests succeeded later when I retried them, and according to our logs, the failures were due to timeouts trying to load the data, presumably because of high usage/load at that time

Re: UNEXPECTED_INTERNAL_API_ERROR at ConversionTrackerService.get()

2015-09-01 Thread Zweitze
Josh, What we do with the errors, where a retry doesn't help? We fail - we can't complete the task, so we log the problem. Using that log I ask what this error was about - because, sometimes it's about a new AdWords feature not correctly implemented in the API. Zweitze. On Thursday, August 27

Re: UNEXPECTED_INTERNAL_API_ERROR at ConversionTrackerService.get()

2015-08-27 Thread Josh Radcliff (AdWords API Team)
Hi Zweitze, The underlying error here was basically a time out when trying to read the data, so unlike with rate limits, we (unfortunately) can't return a recommended wait period for retry in the exception. You mentioned that your current retry approach fixes about 50% of these errors. What do

Re: UNEXPECTED_INTERNAL_API_ERROR at ConversionTrackerService.get()

2015-08-26 Thread Zweitze
Hi Josh, Thanks for your answer. The situation here is that we cannot afford to wait much longer. If you said that three minutes waiting may have produced better results we would consider that, but in this case we have not much to work on. What I mean: we noticed that about 50% of this type of

Re: UNEXPECTED_INTERNAL_API_ERROR at ConversionTrackerService.get()

2015-08-26 Thread Josh Radcliff (AdWords API Team)
Hi Zweitze, In your retry policy, you may want to implement an exponential back-off policy, so that each retry attempt waits longer than the previous one. I just tried your request again and it succeeded, which further suggests that this was a temporary issue. Aside from the request ID you men

Re: UNEXPECTED_INTERNAL_API_ERROR at ConversionTrackerService.get()

2015-08-26 Thread Zweitze
Josh, Indeed the software retried. After 30 seconds the call was tried again, which also failed, and then two more retries after waiting 30 seconds each time. So in total there were four attempts in 90 seconds. The response I sent was the response of the last attempt. (Unfortunately we don't re

Re: UNEXPECTED_INTERNAL_API_ERROR at ConversionTrackerService.get()

2015-08-25 Thread Josh Radcliff (AdWords API Team)
Hi Zweitze, Looking at our logs, this appears to be a transient error on our side. Did you retry the request some time after the initial set of retries, and if so, did it ever succeed? Thanks, Josh, AdWords API Team On Tuesday, August 25, 2015 at 8:03:04 AM UTC-4, Zweitze wrote: > > Hi all, >

UNEXPECTED_INTERNAL_API_ERROR at ConversionTrackerService.get()

2015-08-25 Thread Zweitze
Hi all, This morning we received an UNEXPECTED_INTERNAL_API_ERROR while calling ConversionTrackerService.get(). We retried the call three more times, but the error persisted. What's going on? The exception we received: https://adwords.google.com/api/adwords/cm/v201502";> [InternalApiE