Hi

I've had a search through the manuals and can't find answers to these questions about JOBS.

1.  How often does the server check to see if there are JOBs to execute?  If I create a JOB now to run say ...

BETWEEN TIME '13:00' AND TIME '13:30' and the time is now 12:59, can I expect to run in a minute's time or will I have to wait for a whole day.

2.  If the server is stopped for some reason, does it pick up the JOBs that should have run in the down period and run them in order or are they lost and gone forever (like Clementine)?

Cheers

Jeff

On 12/1/2014 5:11 PM, Jeff Cook wrote:
> 1.  How often does the server check to see if there are JOBs to execute?  If I create a JOB now to run say ...

It's approx 1 per minute rfom what i can see. It's also the smallest
interval so we know it must run at least once per minute.

> BETWEEN TIME '13:00' AND TIME '13:30' and the time is now 12:59, can I expect to run in a minute's time or will I have to wait for a whole day.

It should run within 1-2 minutes. Server check jobs once per minute so
in worst case it'll check it around 59 second mark and your job might
run at 13:00:59. The timing is set on server start so it might instead
check at 1 seconds mark in which case your job might run at 13:00:01.

This is the case with most intervals but for 'every' X minutes interval
you get additional runs (i.e. for every 5 minutes you should get runs at
13:00:59, 13:05:59, 13:10:59, etc until your 13:30 end time)


> 2.  If the server is stopped for some reason, does it pick up the JOBs that should have run in the down period and run them in order or are they lost and gone forever (like Clementine)?

It does not run missed jobs. So f you start the server at 13:31 then it
won't run the job with end time of 13:30.

However if you start the server when scheduled time is still active (say
13:20) then it will run the job as normal at least once (and then
continue with regular interval).

Raul

Thanks Raul for clarifying that.

It all makes sense, I think

Cheers

Jeff

On 2/12/2014 5:08 p.m., Raul wrote:
> On 12/1/2014 5:11 PM, Jeff Cook wrote:
>> 1.  How often does the server check to see if there are JOBs to
>> execute?  If I create a JOB now to run say ...
>
> It's approx 1 per minute rfom what i can see. It's also the smallest
> interval so we know it must run at least once per minute.
>
>> BETWEEN TIME '13:00' AND TIME '13:30' and the time is now 12:59, can I
>> expect to run in a minute's time or will I have to wait for a whole day.
>
> It should run within 1-2 minutes. Server check jobs once per minute so
> in worst case it'll check it around 59 second mark and your job might
> run at 13:00:59. The timing is set on server start so it might instead
> check at 1 seconds mark in which case your job might run at 13:00:01.
>
> This is the case with most intervals but for 'every' X minutes interval
> you get additional runs (i.e. for every 5 minutes you should get runs at
> 13:00:59, 13:05:59, 13:10:59, etc until your 13:30 end time)
>
>
>> 2.  If the server is stopped for some reason, does it pick up the JOBs
>> that should have run in the down period and run them in order or are
>> they lost and gone forever (like Clementine)?
>
> It does not run missed jobs. So f you start the server at 13:31 then it
> won't run the job with end time of 13:30.
>
> However if you start the server when scheduled time is still active (say
> 13:20) then it will run the job as normal at least once (and then
> continue with regular interval).
>
> Raul

Jeff

Just adding to Raul's comment, note that if you have a lot of jobs scheduled i.e. 9am - 6pm, 12 midday - 6pm etc., and then you switch the server on at 12.01 _all_ the jobs which are due to run will start.

Its only a small thing, but it can mean a lot of jobs kicking off at the same time if you re-start the server.

On 4/12/2014 10:58 p.m., Adam Brett wrote:
> Jeff
>
> Just adding to Raul's comment, note that if you have a lot of jobs scheduled i.e. 9am - 6pm, 12 midday - 6pm etc., and then you switch the server on at 12.01 _all_ the jobs which are due to run will start.
>
> Its only a small thing, but it can mean a lot of jobs kicking off at the same time if you re-start the server.
>
Thanks Adam - something more to keep in mind.

Cheers

Jeff