To add to this problem is the fact that I can't adequately catch the exception and avoid the re-queueing of the task. More on that here...
http://groups.google.com/group/google-appengine/browse_thread/thread/288966daaecf3d05/c70bfd5b7f3307ef#c70bfd5b7f3307ef On Oct 29, 2:17 pm, Joshua Smith <[email protected]> wrote: > Well that's not cool. > > Task queue did the same thing: Threw an exception, even though it > actually queued the task. Perhaps Google is confused about what an > exception is. > > Nick: How can I tell if the email was sent? I'd hate to blast a bunch > of duplicate emails just because of some bogus error. > > Perhaps you should just increase the "Timeout" on this API to a limit > that it can actually meet? > > -Joshua > > On Oct 29, 2009, at 2:32 PM, Greg Tracy wrote: > > > > > I'm seeing quite a few as well. Although I do find that the emails get > > delivered regardless. > > > On Oct 29, 11:22 am, Joshua Smith <[email protected]> wrote: > >> We're getting a surprising number of these errors: > > >> "The API call mail.Send() took too long to respond and was > >> cancelled." > > >> This is happening, for example, when we send an email to three people > >> in the to: list. Billing is enabled in my app. > > >> Should I wrap the call to mail.send_mail with an a try/except/retry > >> loop? > > >> -Joshua > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
