Google:MCC report failure does not stop processing

On 2-11 when running the morning MCC report, the output was:

2009-02-11 03:50:00.278 (3) [main]: Debug Level set to 3
2009-02-11 03:50:00.287 (3) [main]: =============== Starting Google MCC Report
================
2009-02-11 03:50:00.290 (3) [main]: === Starting TSA MCC account ===
2009-02-11 03:50:00.290 (3) [main]: Using filename:
/var/local/tsa/sedata/google/tsa-mcc-report-2009-02-10.xml.gz
2009-02-11 03:50:00.314 (3) [main]: Passed null searchEngineUser, connecting
user TSA master username/password
2009-02-11 03:50:01.062 (3) [main]: Created shared sesystem connection rw
2009-02-11 03:50:02.504 (3) [main]: Downloading MCC report...
2009-02-11 03:50:02.508 (3) [main]: validating report job...
2009-02-11 03:50:06.911 (3) [main]: ...success
2009-02-11 03:50:07.507 (3) [main]: Scheduled report. Report Job ID = 1262042970
2009-02-11 08:45:18.657 (3) [main]: Connected to URL
"https://adwords.google.com/api/adwords/ReportDownload?t=AAAAAEs5P1oAAAEfZjprCwEAAAAAPrH3GziZ7CW56ssk8qoKUIre4uq91s-O"
2009-02-11 08:56:32.474 (2) [main]: Other I/O Exception pulling
"https://adwords.google.com/api/adwords/ReportDownload?t=AAAAAEs5P1oAAAEfZjprCwEAAAAAPrH3GziZ7CW56ssk8qoKUIre4uq91s-O"
into "/var/local/tsa/sedata/google/tsa-mcc-report-2009-02-10.xml.gz"
2009-02-11 08:56:32.476 (3) [main]: MCC report download (Tue Feb 10 00:00:00 PST
2009, "/var/local/tsa/sedata/google/tsa-mcc-report-2009-02-10.xml.gz") ->
success:false
2009-02-11 08:56:32.476 (3) [main]: === Completed TSA MCC account ===

Even though sucess was false, the process still continued running the extra MCC
report for fonality and then sesummarizer. If it had stopped and alerted someone
of the error, we could have avoided some problems ....

Murty - I spoke with Jeff who suggested you look at this as a part of the Google
report project. It is not a huge priority as this has happened only once since I
have been at TSA but it would be better it did not happen again