I think that is from an old version of the documentation when the Task Queue was an experimental feature. The current version of documentation does not match ( https://developers.google.com/appengine/docs/java/taskqueue/overview-push). It says:
When implementing the code for tasks (as worker URLs within your app), it > is important to consider whether the task is > idempotent<http://en.wikipedia.org/wiki/idempotent>. > App Engine's Task Queue API is designed to only invoke a given task once; > however, it is possible in exceptional circumstances that a task may > execute multiple times (such as in the unlikely case of major system > failure). Thus, your code must ensure that there are no harmful > side-effects of repeated execution > I do not think you have to worry about tasks being lost or dropped (if used correctly). On Thursday, July 12, 2012 12:17:07 AM UTC-4, Richard Arrano wrote: > > I also have not seen tasks fail to run, but I found this thread: > > > http://stackoverflow.com/questions/5583813/google-app-engine-added-task-goes-missing > > Specifically, the part that says: "Tasks are not guaranteed to be executed > in the order they arrive, and they are not guaranteed to be executed > exactly once. In some cases, a single task may be executed *more than > once or not at all*." > > I haven't seen the behavior myself, and perhaps the commenter is not > correct, but it occurred to me that I need to account for the > possibility. I believe I will have a status flag a la Per's > suggestion. 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/-/p9XOOb8YBlUJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
