You're confusing two different things. When the task successfully completes, it's removed from the queue. However, a "tombstone" is left behind to allow you to use task names to enforce "once only" semantics. You almost certainly shouldn't rely on being able to execute a task with the same name ever again, even if the tombstone might be removed after a week. If you want to execute a task, say, at most once a day, append the date to the task name.
A very good introduction can be found in the Google I/O video on offline processing ( http://www.youtube.com/watch?v=o3TuRs9ANhs ). On Sep 24, 12:25 am, gimme <[email protected]> wrote: > I checked my log , and the server returns a HTTP 200 reply > As the doc said, the task may be removed a week later? and there's no > way to NOTIFY the task with the same name to be executed again in > these days. - - > > "POST /task_test HTTP/1.1" 200 124 "AppEngine-Google; (+http:// > code.google.com/appengine)" > > On Sep 23, 1:40 am, stelg <[email protected]> wrote: > > > Maybe the executed task has an error or does it respond a 303 HTTP > > code? > > > To empty the task queue make sure that the Task function that is > > executed returns ONLY a HTTP 200 reply. (Put simple dummy code and > > upload this) > > That works fine. The queue will be made empty. Check your LOG in de > > admin console select the DEBUG option. > > > My framework did automatically access a CSS file. So the function > > caused 2 HTTP GETs, one that I coded myself and one that the framework > > generated. That HTTP GET for the CSS file was returning a 304 code > > causing the task not to run, while my own code returned a proper HTTP > > 200. > > So I stripped the Task function and made sure no CSS file was going to > > be read. That solved my problem. My advice: first check the log and > > try to clean your Task queue as described above > > > On 22 sep, 10:21, gimme <[email protected]> wrote: > > > > I just use GAE to host a simple Blog, and I use Task to update my > > > reply list . > > > > My idea is : every time a reply is posted , I just trigger a Task to > > > add into the queue to update the reply list. I just add a task with > > > the blog's subject id , and the task is executed some time later , > > > maybe 5 seconds after the post is replyed. > > > > And, when someone else post a new reply in the near time , I just add > > > a task with the same name if the task is already in queue , so the > > > task will executed only once. > > > > But i found that even if the Task is executed , It's not removed from > > > the Queue. We could not re-add it. > > > > Why there's no mechanism to NOTIFY the Task to be re-executed ? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
