Hello,
Yes, it was recently fixed. So, you should be seeing better performance on
this. If it's still persisting for you, could you start a new forum thread
with some information of what is going on specifically for you? You may
have a narrow case that may be affecting you at the moment.
Hi there,
Just curious if this has been fixed as we run into similar time out issues.
Thanks!
On Friday, February 8, 2019 at 11:44:05 PM UTC+1, googleadsapi-forumadvisor
wrote:
>
> Hello All,
>
> I just wanted to give an update that we are actively working on this. It
> appears to be
Hello All,
I just wanted to give an update that we are actively working on this. It
appears to be affecting just this report and only specific customers. We
are working on trying to find the source of the issue, which appears to be
a bit tricky. I'll give updates as soon as I have more news.
Hi Luis,
Yes, confirmed it is the GEO_PERFORMANCE_REPORT. If I impose more strict
limitations on the report I can get it in a little under 2 minutes, but
it's not usable for our report.
Thanks,
Ian
On Wednesday, January 23, 2019 at 3:46:41 PM UTC-5, Luis wrote:
>
> Hi there,
>
> We have
Hello Ian,
Could you please confirm if you're downloading the GEO_PERFORMANCE_REPORT
and seeing the issue? If so, this is a known issue and our team is looking
into this. If not, could you please share the API SOAP logs so I can
troubleshoot this further? You can reply back via Reply privately
Chiming in we are the same issue.
On Wednesday, January 23, 2019 at 3:46:41 PM UTC-5, Luis wrote:
>
> Hi there,
>
> We have started to notice huge latencies when querying the
> GEO_PERFORMANCE_REPORT for certain accounts of our customers with
> significant activity / data.
>
> We are using the
We see the same problem here. This report took around 60-90 seconds to
download, it takes now more than 2 hours and fails.
On Wednesday, 23 January 2019 21:46:41 UTC+1, Luis wrote:
>
> Hi there,
>
> We have started to notice huge latencies when querying the
> GEO_PERFORMANCE_REPORT for certain
Hello all,
Thank you for sharing the details privately. I have passed this information
to our Engineering team. I will keep you posted on the updates.
Regards,
Bharani, AdWords API Team
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
Hi Bharani,
I sent you a private message with the account ID I've used to generate the
problem with the awql query. It fails all the time using this query.
I don't think there is more traffic on this account thatn in 2018, so that
is really strange that it's starting to fail right now.
Please
Hi,
We are seeing the same high latency errors, started 24 hours ago.
It seems to happen on the GEO_PERFORMANCE_REPORT table.
I can reproduce the timeout all the time by running this query on some of
the accounts I have access to:
--
select
CityCriteriaId, Clicks,
Hi Bharani,
We are sorry to insist, but this is issue has started to damage our
reputation. Many of our customers are complaining about it, and even a
couple of them have decided to switch to a different reporting tool.
We decided to set the ReportDownloadedTimeout to 5 minutes, a more than
Hello Luis,
Could you please confirm if you're still facing an issue? The report
download requests may time out on extremely large data sets. There is no
explicit data size limit; however, due to a variety of factors, the server
may return an error if the report is too large. If so, could you
12 matches
Mail list logo
