Wonderful, thanks Dave! This is probably the correct approach for me to take.
And that is a fair point, I think for the most part I organised it like that to prevent drift (though I do know of the preventdrift argument to schedule_task()) and ensure that the task always queued for 2200 the next day. That said, looking at the problem with fresh eyes it does seem to be a simpler and more sensible option just to use the built-in rescheduling function. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/7f727cf5-c854-48e6-bcc4-a175184e9a66%40googlegroups.com.
