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 you do with the remaining 50% for other services, and can you do something similar for the *ConversionTracker.get* case? Thanks, Josh, AdWords API Team On Wednesday, August 26, 2015 at 11:58:55 AM UTC-4, Zweitze wrote: > > 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 error disappear > when retrying using our current retry-strategy (this figure is about all > errors with retries, including HTTP 50x). If you would have suggested a > retry-strategy with significant better results in a short time we would > consider that. > > BTW It would be great if this error came with a suggested waiting period, > as some other errors do. > > We experienced tons of UNEXPECTED_INTERNAL_API_ERROR errors, but this was > the first time with ConversionTrackerService.get(). > > > > On Wednesday, August 26, 2015 at 5:00:19 PM UTC+2, Josh Radcliff (AdWords > API Team) wrote: >> >> 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 mentioned, have you seen this occurring on >> multiple occasions? >> >> Thanks, >> Josh, AdWords API Team >> >> On Wednesday, August 26, 2015 at 4:48:52 AM UTC-4, Zweitze wrote: >>> >>> 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 record >>> errors when a retry will come up.) >>> >>> About that same time, say within five minutes, the same call was issued >>> for other accounts - and succeeded. >>> >>> This particular piece of software has no UI, but runs somewhere on a >>> server. It cannot call help from an operator, it can only retry or abandon. >>> Is our retry strategy the right one? Or would a slightly modfied >>> retry-scheme give better protection against these glitches? >>> >>> >>> On Tuesday, August 25, 2015 at 6:14:17 PM UTC+2, Josh Radcliff (AdWords >>> API Team) wrote: >>>> >>>> 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, >>>>> >>>>> 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: >>>>> <detail> >>>>> <ApiExceptionFault xmlns=" >>>>> https://adwords.google.com/api/adwords/cm/v201502";> >>>>> <message>[InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ >>>>> com.google.ads.api.services.common.error.InternalApiError.<init>(InternalApiErro]</message> >>>>> >>>>> >>>>> <ApplicationException.Type>ApiException</ApplicationException.Type> >>>>> >>>>> <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>>>> xsi:type="InternalApiError"> >>>>> <fieldPath> >>>>> </fieldPath> >>>>> <trigger> >>>>> </trigger> >>>>> >>>>> <errorString>InternalApiError.UNEXPECTED_INTERNAL_API_ERROR</errorString> >>>>> >>>>> <ApiError.Type>InternalApiError</ApiError.Type> >>>>> <reason>UNEXPECTED_INTERNAL_API_ERROR</reason> >>>>> </errors> >>>>> </ApiExceptionFault> >>>>> </detail> >>>>> >>>>> Response headers we received: >>>>> RequestId >>>>> 00051e1ae5e0cfe00a0de108b6048a22 >>>>> ResponseTime >>>>> 11807 >>>>> >>>>> The call was made for account 182-109-9525. >>>>> >>>>> >>>>> Any idea what caused the error? >>>>> Thanks in advance! >>>>> >>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/a10e55ad-c46d-4cd8-88e5-64f6a8189fad%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
