Schedule

A schedule owns a trigger definition. It creates runs at configured times or at one configured time. Schedules exist because scheduled work has two separate concerns: when work starts and what work does. The schedule owns the trigger. The target owns the business logic.

​

Characteristics

• A trigger defines when work starts.
• A target defines what work runs.
• Each trigger creates a run.
• Pausing or deleting the schedule affects future runs, not the task or workflow definition.

​

Boundary

This keeps scheduling separate from execution. Use a schedule when work should start automatically. Put the work in a task or workflow and let the schedule trigger it.

​

Wrong fit

Do not put the work itself in the schedule definition. Use a one-time schedule for delayed one-off work and a cron-style schedule for recurring work. For implementation steps, see Runs.