On Monday, March 28, 2016 at 12:38:03 PM UTC-7, Niphlod wrote:
>
> The specific issue with this case is that the scheduler tracks how many 
> times a task has been executed and prevents your "repeats=1" task to be 
> executed again because times_run is probably exceeding the value. 
> That being said (i.e. you'd need to reset times_run too) be aware that 
> modifying scheduler_task records is not supported: if the underlying tables 
> will change (thing that can totally happen in a future release) your code 
> won't work.
>
>
Better to unqueue the task, and requeue, I would think.

But as I read the original post, I thought Arun was trying to run the task 
at an earlier time than he had originally scheduled, so I wouldn't expect 
times_run to have been in play.

/dps



 

> On Saturday, March 26, 2016 at 2:40:50 AM UTC+1, Dave S wrote:
>>
>>
>>
>> On Friday, March 25, 2016 at 4:46:22 PM UTC-7, Arun Kumar wrote:
>>>
>>> Hi,
>>>    I'm using scheduler to run different jobs everyday. To create a new 
>>> job I simply insert into scheduler_task table like below,
>>>
>>> db.scheduler_task.insert(function_name = "run_job", task_name = "job1", 
>>> repeats = 1, period = 86400, start_time = start_time, stop_time = end_time, 
>>> prevent_drift = True)
>>>
>>> The scheduled jobs are running as expected. Say if I want to modify my 
>>> job1 which I inserted above how can I do? If I open the appadmin db and 
>>> modify the start_time to a current time + few secs/mins the next schedule 
>>> not triggered. How can I achieve this? 
>>>
>>
>>
>> Works for me, but I have a repeating task and I'm changing next_run_time. 
>>  Is your status field "QUEUED"?
>>
>> /dps
>>  
>>
>

-- 
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.

Reply via email to