Hello Tim,
So yesterday's occurrence is actually something that the core
engineering team knows the root cause of. There was a loss of
connectivity between one particular set of AdWords API servers and the
backend data store that contains reports data yesterday morning for
several hours. There i
We had a reoccurence of this error at 7:30AM PST.
Thanks.
Tim Ozor
On Oct 14, 12:30 pm, AdWords API Advisor
<[EMAIL PROTECTED]> wrote:
> I wanted to update folks after speaking to the engineering team about
> this again.
>
> There's speculation that these bad URLs might be returned during a
I wanted to update folks after speaking to the engineering team about
this again.
There's speculation that these bad URLs might be returned during a
period of time in which the backend datastore is in a particular state
(apologies for not being able to get more specific than that). They're
matchi
I saw it several times on Friday during the day, but have not seen it
since then.
Tim Ozor
On Oct 2, 10:07 am, AdWords API Advisor <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> The bug is in with the engineering team, but there's no update on it
> yet. How frequently are folks experiencing this b
Hello,
The bug is in with the engineering team, but there's no update on it
yet. How frequently are folks experiencing this behavior over the past
day or so? If this was taking place primarily last week that's a good
data point to pass back to the engineers.
Cheers,
-Jeff Posnick, AdWords API T
Please let us know when this is resolved. In the mean time we've
implemented a re-try ordering a new report if the download url throws
404 not found. The problem with this is we are paying quota for each
new report although the problem is not on our side.
regards,
Albert
--~--~-~--~~-
I am also seeing these errors today with some frequency.
Tim Ozor
On Sep 26, 10:43 am, AdWords API Advisor
<[EMAIL PROTECTED]> wrote:
> Thanks for providing those logs and report job ids. I'll open a bug
> with the reports team with that info.
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
Thanks for providing those logs and report job ids. I'll open a bug
with the reports team with that info.
Cheers,
-Jeff Posnick, AdWords API Team
On Sep 26, 2:50 am, Albert <[EMAIL PROTECTED]> wrote:
> I confirm, we are having this issue in the past several days a lot.
> Happens sporadically.
>
I confirm, we are having this issue in the past several days a lot.
Happens sporadically.
In the part of the trace, you can see we re-try getting a different
download url several times.
===(not found trace + soap log)===
=not fount==
Utilitie
I'm actually seeing this issue quite a bit - I've just been asked to
look into it because of the high number of 'URL not found' issues.
What could be causing this? Too many concurrent connections /
reports / logins / something?
As noted above, the URL we're getting is coming straight from
getGzip
10 matches
Mail list logo
