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 week. Baby sitting my
application over the weekend is getting old.
Thanks for your help.
Tim
On Aug 21, 3:09 pm, AdWords API Advisor <[EMAIL PROTECTED]>
wrote:
> Thanks, I got pinged back from the reports team asking if there was a
> more recent example. I'll provide that report id to them.
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
> On Aug 21, 3:45 pm, tozor <[EMAIL PROTECTED]> wrote:
>
> > Jeff,
>
> > Just letting you know that the problem does still exist, although I
> > went for a couple of days without seeing it. The latest stuck report
> > id is 474410941. However I had to kill the process to keep my
> > application users happy. The report completed on the subsequent
> > attempt within a minute (the stuck report ran for about 40 minutes
> > before I had to kill it).
>
> > Thanks again for looking into this.
>
> > Tim
>
> > On Aug 19, 12:00 pm, tozor <[EMAIL PROTECTED]> wrote:
>
> > > I saw the problem on Sunday night and was going to wait until Monday
> > > morning to post with an updated report id. I have not seen the
> > > problem in the last two days. However I also backed down the
> > > concurrency to three concurrent reports in one part of my application
> > > where it is super critical for me not to have a stuck report. There
> > > is another part of my application where I left the concurrency at 5
> > > reports (both of these are down from 10).
>
> > > I will re-post on the next re-occurrence to let you know if the
> > > problem still exists. Thanks for checking in.
>
> > > Tim
>
> > > On Aug 19, 11:51 am, AdWords API Advisor
>
> > > <[EMAIL PROTECTED]> wrote:
> > > > Hello Tim,
>
> > > > I'm sorry that there's no significant update from the reports team
> > > > yet, but I did want to check in to see if the behavior has changed at
> > > > all since last week. I can understand the need to manually cancel the
> > > > offending reports to ensure that your clients get the retried reports
> > > > in a timely manner, so in the interim you shouldn't hesitate to cancel
> > > > them and retry. If the reports team comes back to me saying that they
> > > > need a "live" example I'll sync up with you about that.
>
> > > > Cheers,
> > > > -Jeff Posnick, AdWords API Team
>
> > > > On Aug 15, 6:00 pm, tozor <[EMAIL PROTECTED]> wrote:
>
> > > > > Again thanks for the reply. One complicating factor is that I can't
> > > > > let a job remain stuck indefinitely because it backs up my
> > > > > application. At most I have about four hours after a post that I can
> > > > > wait. If you folks were in the middle of debugging it, then I can let
> > > > > it stay stuck, otherwise in the interest of my application users I am
> > > > > forced to kill the process and reissue the report. As far as the
> > > > > report ids you mentioned:
>
> > > > > 421168971 - this completed after about 50 minutes, again this is
> > > > > highly abnormal since it usually takes 1 minute
> > > > > 471606181 - I had to kill this one after 2.5 hours.
> > > > > 471187411 - I had to kill this one after 90 minutes
> > > > > 471986881 - This was the one I reported today and I let it go for
> > > > > almost 4 hours before I had to kill it.
>
> > > > > I will say that the accounts in question are very large and this may
> > > > > be a contributing factor. From my black box perspective it seems like
> > > > > you folks have code which predicts the cost of reports and doesn't let
> > > > > the resource cost from a single user exceed a certain limit. It seems
> > > > > like the jobs which get queued up as a result of the resource cost
> > > > > never get started. I am thinking that these jobs get cleared from the
> > > > > queue when the session goes away when I kill the process. Clearly I
> > > > > am guessing here but this is the type of behavior I see on my end.
>
> > > > > I will continue to post stuck job ids to this thread if that is useful
> > > > > for you. If not let me know so that I don't spam the group too much.
>
> > > > > Tim
>
> > > > > On Aug 15, 4:33 pm, AdWords API Advisor <[EMAIL PROTECTED]>
> > > > > wrote:
>
> > > > > > Hello Tim,
>
> > > > > > 421168971 completing successfully should not have been the result
> > > > > > of
> > > > > > any special intervention on our end, no. How long did it take before
> > > > > > it finally was marked as complete? And what about 471606181?
>
> > > > > > Okay, thank you for the debugging that you're doing on your end.
> > > > > > I've
> > > > > > only heard back about 471187411, and that job did not complete
> > > > > > properly on our end, so it's not a question of the job completing
> > > > > > but
> > > > > > the wrong status being returned back. I have not heard anything
> > > > > > about
> > > > > > what the potential cause of the problem is yet unfortunately, so I
> > > > > > can't provide any concrete recommendations as to how to work around
> > > > > > it
> > > > > > at this time. I will update the open bug with the latest job id
> > > > > > though.
>
> > > > > > Cheers,
> > > > > > -Jeff Posnick, AdWords API Team
>
> > > > > > On Aug 15, 12:28 pm, tozor <[EMAIL PROTECTED]> wrote:
>
> > > > > > > Sorry to be a pain about this, but this is becoming a real issue
> > > > > > > with
> > > > > > > my application. I have been successfully running multiple
> > > > > > > concurrent
> > > > > > > keyword status reports since V10 and all the way thru V12. Now
> > > > > > > seemingly without reason (at least as far as my existing
> > > > > > > application
> > > > > > > code goes) I am getting these situations where the report stays in
> > > > > > > progress forever. I have tried reducing the number of concurrent
> > > > > > > jobs
> > > > > > > and even putting a wait between each report request. So far this
> > > > > > > has
> > > > > > > not been successful. Again, I can kill the process and issue the
> > > > > > > same
> > > > > > > report request as the one which was stuck and it completes within
> > > > > > > a
> > > > > > > minute or two. While this is a workaround, it means that I have
> > > > > > > to
> > > > > > > monitor my application multiple times a day looking for stuck
> > > > > > > reports
> > > > > > > because the lack of synchronized data in my db has adverse
> > > > > > > downstream
> > > > > > > effects for my application.
>
> > > > > > > My current stuck report is job id 471986881. Hopefully I can get
> > > > > > > an
> > > > > > > update from you folks as to whether you in fact believe there is a
> > > > > > > problem on your end or if there is something truly strange
> > > > > > > happening
> > > > > > > on my end. What would take the guess work out of the equation is
> > > > > > > if
> > > > > > > someone on your report team can look in the logs and see what the
> > > > > > > Adwords server side thinks is the status of this particular
> > > > > > > report.
> > > > > > > If it is still in progress, then why is it taking so long? If the
> > > > > > > server side thinks it is complete, then at least it focuses the
> > > > > > > debug
> > > > > > > effort.
>
> > > > > > > Again I very much appreciate this forum and the Adwords API has
> > > > > > > been
> > > > > > > very reliable for us up until this issue. Unfortunately I don't
> > > > > > > know
> > > > > > > how to proceed without some help from someone who can look in the
> > > > > > > logs
> > > > > > > on the back end.
>
> > > > > > > Tim
>
> > > > > > > On Aug 14, 11:59 am, tozor <[EMAIL PROTECTED]> wrote:
>
> > > > > > > > FYI one of them completed (421168971) and I'm not sure if this
> > > > > > > > was
> > > > > > > > divine intervention on your end. 471606181 remains in
> > > > > > > > progress.
>
> > > > > > > > Tim
>
> > > > > > > > On Aug 14, 11:37 am, AdWords API Advisor
>
> > > > > > > > <[EMAIL PROTECTED]> wrote:
> > > > > > > > > Thanks, Tim, if you don't mind leaving them InProgress I do
> > > > > > > > > think that
> > > > > > > > > would be helpful. I have managed to engage someone from the
> > > > > > > > > reports
> > > > > > > > > team to look into this so hopefully you won't have to leave
> > > > > > > > > them
> > > > > > > > > InProgress for too long a time.
>
> > > > > > > > > Cheers,
> > > > > > > > > -Jeff Posnick, AdWords API Team
>
> > > > > > > > > On Aug 14, 12:13 pm, tozor <[EMAIL PROTECTED]> wrote:
>
> > > > > > > > > > Unfortunately limiting the concurrency to 5 reports did not
> > > > > > > > > > solve the
> > > > > > > > > > problem. I have two report ids (471606181 and 421168971)
> > > > > > > > > > currently
> > > > > > > > > > being reported as In Progress which I don't believe will
> > > > > > > > > > ever finish.
> > > > > > > > > > I'll let it run as long as I can in hopes that your
> > > > > > > > > > reporting team can
> > > > > > > > > > explain why they are stuck in Progress.
>
> > > > > > > > > > Thanks again.
>
> > > > > > > > > > Tim
>
> > > > > > > > > > On Aug 13, 10:24 am, AdWords API Advisor
>
> > > > > > > > > > <[EMAIL PROTECTED]> wrote:
> > > > > > > > > > > Thanks, Tim. I'll bring the issue up with the reports
> > > > > > > > > > > team and mention
> > > > > > > > > > > your observations along with that report job id. In the
> > > > > > > > > > > meantime if
> > > > > > > > > > > you believe that scheduling only 7 reports at once is a
> > > > > > > > > > > workaround,
> > > > > > > > > > > I'd encourage you to do that for the time being--I don't
> > > > > > > > > > > know of any
> > > > > > > > > > > limits on the number of concurrent zero impression
> > > > > > > > > > > reports, but it's
> > > > > > > > > > > possible that they're there.
>
> > > > > > > > > > > Cheers,
> > > > > > > > > > > -Jeff Posnick, AdWords API Team
>
> > > > > > > > > > > On Aug 13, 9:35 am, tozor <[EMAIL PROTECTED]> wrote:
>
> > > > > > > > > > > > The problem continues to re-occur. I am wondering if
> > > > > > > > > > > > there is a limit
> > > > > > > > > > > > to the number of concurrent zero impression keyword
> > > > > > > > > > > > status reports I
> > > > > > > > > > > > can run. The particular part of my application where
> > > > > > > > > > > > this is
> > > > > > > > > > > > occurring is issuing 8 concurrent zero impression
> > > > > > > > > > > > reports for the
> > > > > > > > > > > > previous day. Each report is for a different account.
> > > > > > > > > > > > 7 of the
> > > > > > > > > > > > reports complete within two minutes. However the
> > > > > > > > > > > > report for one of
> > > > > > > > > > > > the accounts never seems to complete. In the case this
> > > > > > > > > > > > morning the
> > > > > > > > > > > > report id was 471187411.
>
> > > > > > > > > > > > Once it gets in this state, then no other zero
> > > > > > > > > > > > impression reports can
> > > > > > > > > > > > be run to completion on this account. I have to kill
> > > > > > > > > > > > the process
> > > > > > > > > > > > running the report. Once I kill the process then the
> > > > > > > > > > > > next
>
> ...
>
> read more ยป
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
