If you need to be super-certain, then you will always want to have a status flag that tells you if you have already processed some entity or not. It's also useful for cases where you cannot use transactions (a task might die in the middle as well of course)
Well, at least that's how we do it :) Whenever something is important, we want to track some kind of status anyhow. One of these statuses would be STATUS_UNPROCESSED or so. Cheers, Per On Wednesday, July 11, 2012 1:55:37 PM UTC+2, 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/-/UNIfi6NldFYJ. 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.
