Menu
▾
▴
#186 tasks never executed in PloneMaintenance
It appears that new tasks created in PloneMaintenence
never get executed. They are always created with a
"Last execution time" of 9999. This seems to interfere
with the scheduling algorithm as each task becomes due,
its next execution time is bumped up without executing
the script.
If I hack the resetLastExecutionDate method (called in
the MaintenanceTask init) to use something in the past,
say 2000, instead of 9999, then things start working
properly.
Versions: PloneMaintenance 1.1, Zope 2.8.4-final,
python 2.3.5, Plone 2.1.1
Also using timezone GMT +10, although I doubt that is
relevant.
Logged In: YES
user_id=52290
It may appear that it doesn't work, but in fact, it does.
PloneMaintenance is not executing all of the tasks whenever
you start it. It only does when necessary.
Logged In: YES
user_id=328906
So I was just imagining this defect all along? I'll never
submit a bug report again, just in case I was imagining it.
Did you actually read the report where is said "as each task
becomes DUE, its next execution time is bumped up WITHOUT
executing the script", or did I imagine writing that too.
Fine, I'll just keep using the patch that makes the product
work with things line PloneSUbscription, and you can keep
looking like an incompetant developer. Enjoy.
Logged In: YES
user_id=52290
I'm adding a task and click on "Run maintenance tasks now",
and the task runs:
One script was run. No scripts failed.
What settings did you make on the task?