Hello Eric,
Great, using a thread pool to limit the total number of pending
reports sounds like the right approach. If you previously didn't have
a limit on the total number of pending reports then I'm inclined to
think that was the root cause of the behavior you saw. Once a newly
scheduled repo
Hello Jeff,
Right...we've implemented the semaphore suggestion as a Java thread
pool with a maximum of 5 threads. However, it is unclear to me from
the Report Center documentation as to whether the referenced account
is an MCC account or client account. We've made the assumption it has
been the
A quick followup question: are you doing anything in your code to make
sure that you don't have more than 15 active reports at any one time?
As per
http://code.google.com/apis/adwords/docs/developer/ReportService.html
"The Report Center stores up to 15 generated reports per account. When
the s
Hello Eric,
Thanks for the additional detail about the occurrence rate.
I don't think this is related to the issue in the other thread. It's
pretty easy to trigger that error when you're not supplying the
appropriate MCC/client email credentials, which sounds like is what is
happening in the o
Hello Jeff,
This behavior started about three weeks ago. It happens every day and
effects anywhere from 4 to 10 client accounts out of over 200 client
accounts. If we try again after the failure, we are able to get the
report.
There was another thread started yesterday that is giving the same
Hello Eric,
Yes, that does look very odd. I'm filing a bug about it. You're
saying that this happens at least once a day? When did the behavior
start?
Cheers,
-Jeff Posnick, AdWords API Team
On Nov 10, 3:47 pm, Eric <[EMAIL PROTECTED]> wrote:
> We have been getting a lot of 500 Internal Serve
