Set a schedule and timezone
Choose a cadence and check when the next run is expected.
Select the Schedule trigger category in the routine editor. Choose a cadence and a timezone, then review the displayed next-run information after saving.
Read the visual explanation
A daily routine uses its saved time and timezone. Each scheduled trigger creates a run that links to an Engineering session.
Supported cadences
| Cadence | What you configure |
|---|---|
| Every 30 minutes | The recurring half-hour cadence |
| Hourly | Minute within the hour |
| Daily | Local time |
| Weekdays | Monday through Friday at a local time |
| Weekly | Day of week and local time |
| Monthly | Day of month and local time |
Monthly dates beyond the length of a shorter month use that month's last day. The timezone belongs to the saved schedule; it is not necessarily the timezone of the teammate reading the page.
Make the timezone explicit
Use a named timezone that matches the intended working schedule. A daily 09:00 routine in Asia/Kolkata has a different instant from 09:00 in Europe/London. Daylight-saving rules can change the UTC time associated with a local-time schedule.
After changing a cadence or timezone, save and recheck next run. Do not assume an unsaved editor change affects scheduling or that changing the schedule replays missed work.
Inspect execution separately
A scheduled time records when work is due, not a promise that the agent completes at that exact instant. Capacity, access, model limits, or startup failures can affect execution. Follow the run's status and linked session for the outcome.
Use Test run to verify the saved prompt without waiting. Pause the routine when future scheduled work should stop, and inspect active runs separately.
See manage routines and usage and limits.