I wanted to report an occurrence this morning, and more importantly
the fact that my workaround strategy was successful. Basically here
is what I am doing:
1) Download the file from the URL which is returned from
getGzipReportDownloadUrl()
2) Check the file size. If it is 30 bytes or less, then proceed back
to step #1
So it does not seem necessary to call getGzipReportDownloadUrl() again
to get a different download URL. In my case the same download URL
returned the full file on the second try. In all my failure cases the
size of the file returned is 20 bytes. I chose 30 bytes because
having a slightly higher limit made me feel better. All of my reports
are way larger than 30 bytes.
Hope this helps.
Tim
On Jan 13, 11:17 am, AdWords API Advisor
<[email protected]> wrote:
> Hello,
>
> I'm waiting to hear back from the engineer who's assigned to this
> issue as to what specific information he'd need to debug things in the
> Production environment. The fact that you're deleting the reports
> after an attempted download sounds like it would complicate debugging,
> but I'll let you know.
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
> On Jan 13, 4:56 am, Zweitze <[email protected]> wrote:
>
> > Jeff,
>
> > Thanks for your answer. I'll do the rewrite to retrieve a new URL in
> > case of an error. But it's quite a rewrite so it'll take some time.
>
> > With respect to your question about the time: Most reports are
> > scheduled between 5.30h and 6.00h (European time, GMT-1). In that
> > interval between 30 and 100 reports are scheduled. Recent errors:
>
> > 10th Jan: 6.03h Empty report
> > 11th Jan: 5.41h Empty report
> > 12th Jan: 5.44h Empty report
> > 13th Jan: 5.50h 404 Not Found
>
> > If you'll need repport IDs and RequestIds of getGzipDownloadUrl() let
> > me know. Unfortunately the code is still deleting reports it doesn't
> > need anymore.
>
> > On Jan 5, 8:57 pm, AdWords API Advisor <[email protected]>
> > wrote:
>
> > > Hello,
>
> > > I've investigated this behavior in the past and collected a decent
> > > amount of debugging information. (The fact that your reports are now
> > > deleted would make it more difficult to go through the debugging
> > > steps, but that's okay.) Unfortunately, we've yet to come up with any
> > > conclusive causes for either empty reports or 404 URLs (which appear
> > > to be two distinct issues). If you get to the level of reproducibility
> > > where we can schedule some reports at a specific time that some of the
> > > engineering team is looking at the backend then that would be useful,
> > > but as it is it doesn't sound like it happens often enough.
>
> > > Based on what's worked for other developers, when you encounter
> > > either issue you should be able to call getGzipDownloadUrl() using the
> > > same report ID (assuming you haven't deleted it and that it hasn't
> > > been bumped from the 15 report queue) and get a new download URL that
> > > should give you the full report.
>
> > > Cheers,
> > > -Jeff Posnick, AdWords API Team
>
> > > On Jan 5, 4:55 am, Zweitze <[email protected]> wrote:
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"AdWords API Forum" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
