schedules
GitHub用于配置 Windmill 自动化调度任务，涵盖 cron 表达式格式、文件命名规范及 CLI 同步命令，支持定时运行脚本和流程。
Trigger Scenarios
Install
npx skills add windmill-labs/windmill --skill schedules -g -y
SKILL.md
Frontmatter
{
"name": "schedules",
"description": "MUST use when configuring schedules."
}
Windmill Schedules
Schedules run scripts and flows automatically on a cron schedule.
File Naming
Schedule files use the pattern: {path}.schedule.yaml
Example: f/folder/daily_sync.schedule.yaml
Note: The path is derived from the filename, not stored in the file content.
Cron Expression Format
Windmill uses 6-field cron expressions (includes seconds):
┌───────────── second (0-59)
│ ┌───────────── minute (0-59)
│ │ ┌───────────── hour (0-23)
│ │ │ ┌───────────── day of month (1-31)
│ │ │ │ ┌───────────── month (1-12 or jan-dec)
│ │ │ │ │ ┌───────────── day of week (0-6, 0=Sunday, or sun-sat)
│ │ │ │ │ │
* * * * * *
Common Examples:
0 0 0 * * *- Daily at midnight0 0 12 * * *- Daily at noon0 */5 * * * *- Every 5 minutes0 0 9 * * 1-5- Weekdays at 9 AM0 0 0 1 * *- First day of each month
CLI Commands
Deploying local changes to the workspace can be destructive to remote state — only suggest/run a deploy when the user explicitly asks to deploy/publish/push, not when they say "run", "try", or "test". Deploy via git push or wmill sync push depending on how the repo is wired (see the Deploying section in AGENTS.wmill.md). The commands below never mutate remote state, so they're safe to run yourself — note that sync pull does overwrite local files to match the remote (use sync pull --dry-run to only preview), while schedule just lists.
# Push schedules to Windmill — only when the user explicitly asks to deploy
wmill sync push
# Pull schedules from Windmill
wmill sync pull
# List schedules
wmill schedule
Version History
- 574775d Current 2026-08-20 17:33
