Automation schedules use standard five-part cron expressions in UTC.
How Scheduling Works
The schedule is stored as a cron string in the automation configuration. The engine evaluates that schedule and runs matching automations at the appropriate times.
* * * * * | | | | | | | | | +-- day of week | | | +---- month | | +------ day of month | +-------- hour +---------- minute
Current UI Behavior
Note: The current custom automation UI does not provide a dedicated schedule field or visual cron builder in the basic create/edit screens. If you need to change the schedule for a custom automation, you do it in the configuration itself on the Advanced tab.
New custom automations start with a default schedule value of 0 0 * * 0 in their initial JSON shell.
Common Examples
| Cron | Meaning |
|---|---|
| 0 8 * * * | Daily at 8:00 AM UTC |
| 0 */4 * * * | Every 4 hours |
| */30 * * * * | Every 30 minutes |
| 0 8 * * 1-5 | Weekdays at 8:00 AM UTC |
| 0 0 1 * * | First of every month at midnight UTC |
UTC Time
Schedules run in UTC, not your local timezone. Convert your intended local run time into UTC before saving the schedule.
Example in Config
{
"schedule": "0 8 * * *"
}
Practical Reminder
A schedule only tells SureDone when an automation is eligible to run. You still need a valid automation configuration and the automation must be enabled when you are ready for scheduled runs.