I observed such behavior too. It is reproducible only on production (devserver is fine). I believe it to be a bug or optimization in TaskQueue code. Basically GAE appear not to check back the queue for ready-to-execute tasks after frontend enqueues a new task with 0s or very short delay.
That is based on a couple of observations: 1. If I schedule my tasks with 5+ second delay I do not see that problem. 2. I enqueued 100 dummy tasks to fire every second between now and 100s in the future and ran my tests. Problem was NOT observed GAE Team please comment -- 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.
