Configure Windmill cron schedules using schedule.yaml files and wmill CLI commands.
npx skills add https://github.com/vpzed-dev/smithy --skill schedules-vpzed-dev
Please help me install this Agent Skill. Skill: schedules Source: https://github.com/vpzed-dev/smithy/tree/main/windmill/local-dev/.agents/skills/schedules Command: npx skills add https://github.com/vpzed-dev/smithy --skill schedules-vpzed-dev
*.schedule.yaml schema including cron expression, timezone, script or flow path, retry policies, and failure/recovery handlers. - Cron Expression Guidance: Documents Windmill's 6-field cron format (with seconds) plus common patterns like daily at noon or every 5 minutes. - Safe CLI Operations: Distinguishes read-only commands (wmill schedule, wmill sync pull --dry-run) from destructive deploys (wmill sync push) that require explicit user approval. - Use Case: You need a flow to run every weekday at 9 AM with retries on failure. Create f/folder/morning_job.schedule.yaml with cron 0 0 9 * * 1-5, set is_flow: true, and configure an exponential retry block. ## Quick Start Create a Windmill schedule file that runs my daily_sync flow every day at midnight UTC with a failure handler.High-intent search queries and answers about installing and using this skill.
Create a file named `{path}.schedule.yaml` containing a 6-field cron expression, timezone, script_path, is_flow flag, and enabled status. Deploy it to the workspace with `wmill sync push` or git push.
Windmill uses 6-field cron expressions that include a leading seconds field, unlike standard 5-field cron. For example, `0 0 12 * * *` runs daily at noon, and `0 */5 * * * *` runs every 5 minutes.
Add a `retry` block to the schedule.yaml with either `constant` (fixed delay) or `exponential` (backoff with multiplier and jitter) settings, specifying attempts and seconds between retries.
Yes, set `on_failure` to a script or flow path and use `on_failure_times` to control how many consecutive failures trigger it. You can also define `on_recovery` and `on_success` handlers.
No, `wmill sync pull` overwrites local files to match the remote workspace. Use `wmill sync pull --dry-run` to preview changes first, and `wmill schedule` to list schedules without modifying anything.
windmill-labsWrite Windmill Python scripts with a standard main function and TypedDict resources.
jamesogunsanReview Python background jobs for retries, idempotency, and failure recovery.
digirati-co-ukConfigure BullMQ workers, schedulers, and task routing for Madoc TS queues.
windmill-labsImplements new native trigger services across Windmill's Rust backend and Svelte frontend.