Having no insight about you logic... Agree with other responses that while the timing of a task queue task may be unpredictable, the final execution of said task is pretty certain. If you want more control, then perhaps a pull queue may be an option since you should easily find a means to record/log what is in the queue, and delete the queue items only after your logic has ascertained its final disposition is proven (e.g. completed a put() operation without exception). HTH -stevep
On Wednesday, July 11, 2012 4:55:37 AM UTC-7, Richard Arrano wrote: > > Hello, > I have been designing my app with the notion in mind that even named > tasks may execute more than once, but I only recently came to realize > that a task may not execute at all. I have a task that operates on a > subset of my entities and it's absolutely imperative that all members > of this subset get processed and saved. I originally thought named > tasks would help accomplish this, but this does not seem to be the > case. Is there any way to guarantee that I process these entities? I > also considered a cron job that checks every couple of minutes to > check for unprocessed entities(since a cron job will kick off the > initial task) but I was hoping for a slightly more elegant solution. > > Thanks, > Richard -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Y6aDa5c8YFEJ. 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.
