Hello Tim,
That sounds like a reasonable solution for the time being. I'm going
to leave the bug issue open with the reports team though, and will see
if I get anywhere with following up on that. The discrepancy in the
amount of time it takes the reports to finish is bad, and I'd rather
have it
So I ended up building some defensive logic into my application.
Basically if a report takes longer than 20 minutes, I nuke the thread
which is polling for the results, and issue a new report call. So far
I have seen four cases where this logic triggered and each time the
subsequent report comple
Hello Tim,
Your frustration is understandable, and I wish that there were
greater transparency into what is actually going on to cause these
delays in your reports processing. As it is, what I continue to hear
from the reports engineering team is that the delays in completing the
reports whose i
I'm not having as many problems with this issue as tozor, but I have
seen reports sporadically taking abnormally long to complete recently.
I run a set of reports every morning to get updated performance data,
and usually they complete within a couple minutes. Yesterday I had a
report that took o
So I have one other interesting piece of data. Today I let the
"stuck" job continue to run in hopes that you folks could do some live
debug on your end. The report did finally complete after 9.5 hours.
This is the same report that typically takes one or two minutes.
Hope this helps your report
I appreciate the reply but am frustrated because I don't see from your
answer how I am going to get this resolved. I currently have a report
which is again stuck. Can you at least tell me from your logs when
the Adwords system started generating the report and when the system
completed generatin
Hello Tim,
I unfortunately don't have much by way of new information from the
reports team. Looking into the logs associated with the report job ids
you've specified hasn't given any indication that there's something
abnormal preventing those reports from completing, and they say there
were not
I have a stuck one I'll let go for awhile. The report id is
431736501. It has been running for 2.5 hours. Hopefully your report
team can find out what is going on with this one.
Thanks.
Tim
On Aug 23, 8:14 am, tozor <[EMAIL PROTECTED]> wrote:
> One more example that occurred this morning
One more example that occurred this morning. This time I only had
three concurrent reports. The report ran for 55 minutes before I
killed it. The stuck report id was 428986461. After I killed the
process the next report finished in two minutes.
I hope I can get some resolution to this next wee
