Scheduled Tasks

A Scheduled Task runs a Command or a Flight Plan on selected Servers and/or Jets at a defined interval. A system cron job picks up due tasks and executes them; you can also run a task manually from the form.

Tasks can be linked to specific Servers and Jets (the command or plan runs on each of these). Linking a task to a Server Template or Jet Template causes the task to be automatically added to any newly created server or jet from that template. Custom variable values can be set per task to override Variables when the command or plan runs.

Access Rules

The Scheduled Tasks menu is available only to Managers and Root. Users have no direct access to the model.

Group	Action	Condition
Manager	R	User is in "Users" or "Managers" of the task, or in "Users"/"Managers" of a linked Server, Server Template, Jet, or Jet Template
Manager	CRU	User is in "Managers" of the task
Manager	D	User is in "Managers" of the task and is the creator of the record
Root	CRUD	Any record

Info

CRUD stands for Create, Read, Update, Delete.

Scheduled Task Configuration

Scheduled Tasks are located under Settings > Automation > Scheduled Tasks (Cetmix Tower menu).

Important

Field and tab visibility depend on the user's Access Level. The Access tab is only available to users with Manager and Root access levels.

Main settings

Field	Description
Name	Task name.
Reference	Used for Odoo automation and YAML export/import. Leave blank to generate automatically.
Active	If unchecked, the task is archived and will not run.
Sequence	Order in the list (drag handle in tree view).
Action	Command — run a Command; Flight Plan — run a Flight Plan.
Command	The Command to run. Visible when Action is "Command".
Flight Plan	The Flight Plan to run. Visible when Action is "Flight Plan".
Interval Number	Repeat every x units (must be > 0).
Interval Unit	Minutes, Hours, Days, Days of Week, Weeks, or Months.
Days of Week	When Interval Unit is "Days of Week", select one or more weekdays (Mo–Su). At least one must be selected.
Next Execution Date	When the task is next due to run. Updated automatically after each run.
Last Execution Date	When the task last ran successfully. Hidden while the task is running.

When the task interval is shorter than the system cron interval for scheduled tasks, a warning is shown on the form: the task may run later than expected.

Run Manually (header button) runs the task immediately and reschedules the next run. Available only when the task is not currently running (Manager and above).

Smart buttons and ribbons

• Command Logs — opens command logs for this task. Visible only when Action is "Command".
• Flight Plan Logs — opens flight plan logs for this task. Visible only when Action is "Flight Plan".
• Archived ribbon — shown when the task is inactive.
• Running ribbon — shown while the task is executing.

Servers

Select the Servers on which the command or flight plan will run. The task runs on each selected server.

Server Templates

Link the task to Server Templates so that it is automatically added to newly created servers created from those templates. Execution runs on the servers listed in the Servers tab (and jets in Jets).

Jets

Select the Jets on which the command or flight plan will run. The task runs on each selected jet.

Jet Templates

Link the task to Jet Templates so that it is automatically added to newly created jets created from those templates. Execution runs on the jets listed in the Jets tab (and servers in Servers).

Configuration Values

Configuration Variables and their values for this task. These override variable values when the Command or Flight Plan is executed. Use this to pass task-specific values (e.g. different parameters per schedule) without changing the command or plan definition.

Access

• Users — users who can view this scheduled task (and run it if the UI allows).
• Managers — users who can modify and run the task; creators can delete their own records.

Execution flow

1. A system cron job runs periodically and selects scheduled tasks where Next Execution Date is in the past, the task is Active, and it is not already Running.
2. Each due task is executed: the linked Command or Flight Plan is run on each Server in Servers and on each Jet in Jets, using the task’s Configuration Values as variable overrides.
3. After execution (success or failure), Last Execution Date and Next Execution Date are updated. For Days of Week, the next run is the next selected weekday at the same time; for other interval types, the next run is current Next Execution Date plus the interval.
4. Logs are stored in Command Logs or in the flight plan log, linked to this scheduled task.