Scheduled tasks

A cron-like scheduler. Each task is a record of the BSPK_TASK_MANAGER table; the manager, started by BSPK_STARTUP and run on the server, checks the tasks about once a second and launches those that are due. BSPK_QUIT stops it, along with the workers it launched.

A task

Field	Role
`name`	The task name, which is also the name of the worker it runs in.
`method_name`	The method to run (31 characters at most).
`period`	When, see below.
`param`	An object, passed as the method's only parameter.
`actif`	False: the task never runs.
`executeOnStartup`	Run once at startup, then follow the period.
`executeOnDev`	In DEV mode, only tasks with this flag run.
`force`	Run at the next pass whatever the period (reset to false afterwards).
`lastExecute`	Filled in by the manager.

There is no screen and no configuration file: you add a task by creating the record, once, for instance in an update method or at startup, after checking it does not exist yet:

var $Task : cs.BSPK_TASK_MANAGEREntity
If (ds.BSPK_TASK_MANAGER.query("name = :1"; "NIGHTLY_EXPORT").length=0)
	$Task:=ds.BSPK_TASK_MANAGER.new()
	$Task.name:="NIGHTLY_EXPORT"
	$Task.method_name:="NIGHTLY_EXPORT"
	$Task.period:="0 0 2 * *"      // every day at 02:00:00
	$Task.param:={vl_Days: 7}
	$Task.actif:=True
	$Task.executeOnDev:=False
	$Task.executeOnStartup:=False
	$Task.save()
End if

The period

Up to five space-separated fields, starting with the seconds (this is not the Unix crontab order):

ss  mm  hh  jj  MMM

Field	Values
`ss` (seconds)	0 to 59
`mm` (minutes)	0 to 59
`hh` (hours)	0 to 23
`jj` (day)	1 to 31, or a weekday: `Monday` … `Sunday`
`MMM` (month)	1 to 12

Each field is * (any value), */x (when the value is a multiple of x) or a number. A missing field is not checked: it matches any value.

Period	Runs
`0 /30 * *`	every 30 minutes, at second 0
`0 5 3 * *`	every day at 03:05:00
`0 0 8 Monday`	every Monday at 08:00:00

How it runs

The manager goes through your project's BSPH_CALL_WORKER method, which does CALL WORKER(name; method_name; param). Consequences:

the method runs in your project's context, on the server: it must be one of your methods, or a shared component method;
one worker per task name: a run still in progress delays the next one (calls queue in the worker), two runs of the same task never run in parallel.

A task without a method_name is skipped, and an alert goes out once as an error mail.

The component's tasks

Task	Period	Role
`BSPK_DUMP_WEB`	every 30 minutes	refreshes the site's exchange snapshot (`BWEB/exchange/snapshot`), on a development machine only (a `DEV_PARAMETERS` is present); see Content reconciliation
`BSPK_DUMP_MAIN`	every minute	the quick pass of the date memory, on a development machine only
`CRON_EXPORT_BSPK_HISTORY`	every day at 03:05	archiving of the change history

Good to know