Scheduled Automation

A rule combines three parts: scope, trigger condition (schedule or device metric), and a single action. Each trigger creates a task in the Activity Center. v1.0.0-alpha2

How to open

The Automation section in the sidebar, within the context of the current farm.

How to create a scheduled rule

1. Click Create rule
2. Set Name — a clear name for the rule
3. Set Scope — a device filter (by model, firmware, algorithm, scanning task, Pool account, etc.) or leave empty for all devices on the farm.
4. Select trigger type Schedule
5. Configure the schedule:
   • Recurring — repeating, with selection of weekdays (minimum one)
   • One-time — single, with a specific date
   • Time — execution time
6. Select action: Reboot, Restart, Pause mining, Resume mining, Thermal control, Pool config — for Thermal control and Pool config, a parameter form opens, identical to the corresponding group operation
7. Optionally enable Show notification — a pop-up notification upon trigger
8. Save the rule

Below the schedule fields, a text breakdown is displayed: frequency, time, farm timezone, and the date of the next run.

Rule Card

Each card shows: trigger type icon, name, status (Active/Disabled), trigger and action description, scope, Next run and Last run, history of the last 7 runs (success/error).

Card menu (⋯): Edit, Run Now, Duplicate, Enable/Disable, Delete. Run Now executes the operation immediately, without changing the schedule.

For a disabled rule (Disabled), the card background is visually different, and Next run is not displayed.

How it works

• Scope is calculated dynamically — at the moment of triggering, not at the moment of rule creation. If new devices match the scope conditions at that time, they will also be affected.
• Devices in Service Mode and locked (Lock state) are automatically excluded from any rule execution.
• One-time rule automatically switches to a disabled state after execution.
• An error on individual devices does not interrupt execution on others — the outcome is reflected in the run history as a partial error.

Notes

The farm timezone is not selected in the rule form — it is taken from the farm settings and displayed in the text breakdown.