We expect to reduce the frequency of these repeat executions. There is a
existing issue for this, which we'll update when it rolls out:
http://code.google.com/p/googleappengine/issues/detail?id=1789
--
You received this message because you are subscribed to the Google Groups
Google App Engine
Hi,
Tasks sometimes run multiple times; that's why they should be
idempotent. The docs say 'in exceptional cases,' but myself and
others see tasks (even named tasks!) execute multiple times during
'normal' processing. It is generally not frequent, but it happens.
Naming tasks helps against double insertion only. After task is inserted in
a Queue it still can execute multiple times. My guess it happens when Task
backend crashes. I have seen it a few times.
--
You received this message because you are subscribed to the Google Groups
Google App Engine
I've got an hourly cron, which inits a task. This works well, but I
just noticed for the second time this week what is very likely a bug.
0.1.0.1 - - [17/Feb/2011:23:00:00 -0800] GET /task/init HTTP/1.1 200
ms=22
0.1.0.2 - - [17/Feb/2011:23:01:43 -0800] POST /task/get HTTP/1.1 200
ms=103318
