Ok, I was mislead then. I thought I could use the task name to check if a task is still in the queue, by catching "TaskAlreadyExistsError". What's the best way to know if a task is still queued, then?
Best, Benjamin On 15 Sep 2009, at 00:36, Nick Johnson (Google) wrote: > Hi Benjamin, > > As the docs say, tombstoned tasks stay that way for at least a week. > Generally you should never try and reuse a task name - generate a > task you expect to be unique each time. > > -Nick Johnson > > On Mon, Sep 14, 2009 at 11:19 PM, Benjamin Schuster-Böckler > <[email protected] > > wrote: > > I'm getting these a lot when trying to add new tasks to a queue. My > understanding is that GAE will keep a "tombstone" for a task that > quit "recently", and if I try to add another task with the same name, > it'll bum out. How long is this "tombstone" gonna stay in place? The > tasks that are raising this exception have finished several hours ago. > I can't find any information on this in the docs either. > > Thanks for the info, best, > > Benjamin > > -- > Benjamin Schuster-Böckler > Pear Computer LLP > > 86 Cavendish Road > Cambridge CB1 3AF > United Kingdom > > Company No. OC340192 > VAT No. 971 3948 85 > > > > > > > -- > Nick Johnson, Developer Programs Engineer, App Engine > > > > -- Benjamin Schuster-Böckler Pear Computer LLP 86 Cavendish Road Cambridge CB1 3AF United Kingdom Company No. OC340192 VAT No. 971 3948 85 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
