I thought that it was strongly consistent because in the background the get-by-key was forced into a transaction and that you didn't have to declare it yourself. If it didn't happen so sporadically, I'd test to see whether this fixed the issue!
As you say, if someone could clarify that would be great. If consistency isn't the issue, then it looks to me that the task is being kicked off before the transaction is committed. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.