> ## Documentation Index
> Fetch the complete documentation index at: https://docs.workflowmachine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use schedules

> Run workflows on a recurring schedule for digests, checks, syncs, and other time-based automations.

## When a schedule is the right trigger

Use a schedule when time is what should start the workflow.

This is a strong fit for:

* daily or weekly summaries
* recurring syncs
* periodic checks
* reminder-style automations

If the workflow exists to run at a particular time or interval, a schedule is usually the right starting point.

## Common schedule patterns

Scheduled workflows often work well for:

* weekday digests
* end-of-day summaries
* weekly reviews
* regular data sync jobs
* reminder workflows that run at fixed intervals

The simpler the timing, the easier the workflow is to reason about later.

## Match the schedule to the real need

Choose a frequency that fits the process.

Ask:

* does this need to run hourly, daily, or weekly
* will running too often create noise or unnecessary usage
* is the workflow still useful at that cadence

A schedule that is too aggressive can waste credits and make the workflow harder to trust.

## Keep scheduled workflows practical

The fact that a workflow runs on a timetable does not mean it should be large or complicated.

As with other workflows, it is usually better to start with:

* one clear schedule
* one clear output
* a short sequence of steps

Then refine the workflow after you have seen real runs.

## Test the workflow before relying on the schedule

Do not assume a scheduled workflow is correct just because the timing looks right.

Test:

* the step sequence
* the output
* any app connections
* any AI or branching behavior

Once the workflow logic is stable, the schedule can handle the recurring execution.

## Check scheduled workflows over time

Scheduled workflows are easy to forget because they run in the background.

Review their runs periodically to confirm:

* they are still producing useful output
* they are not firing more often than intended
* downstream systems have not changed in a way that breaks them

The value of a scheduled workflow comes from consistent behavior over time, not just one successful run.