Skip to main content
Use the Repeating Trigger to run workflows on a fixed cadence in your team’s timezone. It’s perfect for daily digests, weekly summaries, or month-end reports.
To add this trigger, ask the AI Agent for the workflow you want. It will create the trigger for you. For any changes you’d like to make, you can either ask the AI or adjust the schedule details manually in the editor.
Repeating trigger configuration

Example: A daily digest running at 9:30 AM in EST.

​
Breakdown

Choose a cadence

Run on a daily, weekly, or monthly schedule. For weekly runs, pick the weekdays to include. For monthly runs, choose a specific calendar day or use an “nth from the end” rule for flexible month-end timing.Need something those can’t do? Pick Cron expression in the Run every menu and type the expression next to Cron:. The editor shows the schedule in plain English, and the Preview tab lists the next runs so you can check it.

Set start time & timezone

Set the start date for the first run plus a local send time (hour, minute, AM/PM) and an IANA timezone (e.g., America/New_York). Dreamlit schedules future runs in that timezone automatically.

Add an end condition (optional)

Keep the workflow running indefinitely or provide a cutoff date/time to stop scheduling new runs.

Skip overlapping runs (optional)

Turn on Skip a run if the previous one is still running to skip a scheduled run while the last one is still going. Skipped runs show up in your run history. Runs with a wait step stay running until the wait ends, so later runs may be skipped.

​
Custom schedules

A custom schedule uses five parts: minute, hour, day of month, month, and day of week. It runs in the timezone you pick.
  • Runs must be at least 15 minutes apart.
  • A day like the 30th skips months that don’t have it. Use L for the last day of every month.
  • Don’t set both a day of the month and a day of the week. When both are set, a day matches if either one matches.
  • When clocks change, a time that doesn’t exist (like 2:30 AM in spring) runs once at the shifted time, and a time that happens twice (in fall) runs once. If several of your times fall in the skipped hour, they run once together.
  • You can also describe the schedule to the AI Agent, for example “every weekday at 8 AM and 6 PM”, and it will fill this in for you.
If a run is missed (for example during an outage), Dreamlit sends at most one late run, and only if it is less than an hour late. It never sends a backlog of missed runs.
The repeating trigger does not output any row data. Add a Data Query step right after it to load recipients or other context before sending notifications.

​
Explore further

Workflow basics

Learn how triggers, steps, and data flow connect in Dreamlit.

Data Query step

Fetch the audience or context you need right after the trigger.