thanks for investigating on this, Brian. This really explains the strange behavior. As a bugfix I'd suggest to consider the failed runs for calculating next_run_time and not just times_run when prevent_drift is True. I guess times_run should not be updated in case of failed task.
Alex -- 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. For more options, visit https://groups.google.com/d/optout.
