Well, I just changed status from FAILED to ASSIGNED. But I think you're right that it probably needs to be set up to never fail.
On Sunday, May 3, 2015 at 5:08:56 AM UTC-7, Niphlod wrote: > > a task doesn't have an API to be "restarted"... I think the real issue is > how did you "restart" it, not web2py code. A recurring task that fails > stops its lifecycle there. > > On Sunday, May 3, 2015 at 8:33:06 AM UTC+2, pbreit wrote: >> >> I think I'm running into a scheduler problem where I have 25 jobs that >> run once per day. Some of them failed and I didn't restart then for a few >> days. I had prevent_drift set to True. I think then what happens is that it >> tries to calculate the next_run_date based on the start_date and >> num_times_run which sets the next_run_date in the past. Not really sure >> what a fix would look like. In the mean time I've set prevent_drift to >> False. >> >> https://github.com/web2py/web2py/blob/master/gluon/scheduler.py#L824 >> > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
