Device Scheduler — How to Use
Introduction
Device Scheduler lets you automate actions on devices in a group. You can run a job once, on a recurring interval, on selected weekdays, or when a device comes online.
Before you start
-
The device must be online when the schedule job triggers, or the job may not run.
-
Each device can have at most 2 active schedules. Devices that already have 2 cannot be selected.
-
Confirm the device’s subscription still has remaining usage for schedule jobs. If usage is exhausted, running a schedule may fail.
Open Device Scheduler
-
Go to the group you want to manage.
-
Go to Group Settings.
-
Select the Schedule tab.
You will see two sub-tabs:
Sub-tab What it shows Scheduled Active / upcoming schedules. You can add, enable/disable, or delete here. Completed Finished schedules (read-only). Enable/disable and delete are not available.
If there are no schedules in the current sub-tab, the list is empty.
Create a schedule
Step 1
-
Stay on the Scheduled sub-tab. (The Add button appears only here.)
-
Click Add button.
-
The create dialog opens.
Step 2 - Select devices
- Select one or more devices from the list.
- Devices that already have 2 schedules are disabled and cannot be selected.
- Click Next.
Step 3 - Configure the schedule
A. Choose when it runs (schedule type)
| Type | What it does | What you set |
|---|---|---|
| At (one-time) | Runs once at a specific date and time | Date and time (must be at least 5 minutes in the future; shown in your local time / UTC offset) |
| Rate | Runs repeatedly at a fixed interval | Interval value and unit (hours or days; minimum interval is 1 hour) |
| Cron (weekly) | Runs on selected weekdays at a set time | Days of the week + time |
| Online status | Runs when the device comes online | No extra timing fields |
B. Choose what it does (task)
| Task | What you need to provide |
|---|---|
| Reboot | Nothing extra |
| Send command | The command to run (Linux or Windows, depending on the platform you selected) |
| OTA | An uploaded artifact for that platform; optional OTA arguments if supported |
C. Optional settings
-
Add a note so others know why this schedule exists.
-
Use the Enable switch to decide whether the schedule starts active (on by default).
-
Click Save.
Step 4 - Review the result
-
Wait for creation to finish. Progress is shown in the dialog.
-
Check the summary:
-
All succeeded
-
Partial success (some devices failed)
-
All failed
-
-
If some devices failed, review the device name, serial number, and error message.
-
Click Done to return to the schedule list.
Tips
-
Make sure the device is online when the schedule job triggers, or the job may not run.
-
Before creating a schedule, confirm the device’s subscription has remaining usage for schedule jobs so the job can be created and run successfully.
-
Create schedules by platform so OTA artifacts and commands match the OS/architecture.
-
Use Online status when you want a job to run as soon as an offline device reconnects.
-
Use Rate or Cron for recurring maintenance (for example, weekly reboot or periodic updates).
-
Use At for a one-off window (for example, a planned maintenance reboot tonight).
-
Keep notes short and clear so the team can audit schedules later.