Set a schedule on a Grok Bot routine

Put a clock on a saved Grok Bot routine so it runs at the next matching time in the Bot timezone you choose. Official Routines covers schedule choices, the Timezone control under Settings → Bot, the five-minute minimum gap, and the rule that saving does not fire a run. Schedules live on desktop under When to run; on the phone you can pause or resume with Active, while editing the schedule stays on desktop. Routines run in the cloud while your laptop is closed. Build the skill and routine first with Save a Grok Bot skill and schedule a routine, then come back here to lock the cadence.

What you need

A Bot that already owns a routine with a clear instruction, desktop access to open View conversation details → Routines, and a timezone decision for where the work belongs. Auto-detect follows this computer; pick a fixed zone when the routine should follow an office clock instead. Keep write actions behind approval, and use Test a Grok Bot routine with a safe input before you trust the first automatic fire. For event wakes instead of a clock, see Set a Slack listener on a Grok Bot routine or Trigger a Grok Bot routine with a webhook.

Pick timezone, schedule, and Active

1. Open Settings, go to Bot, and confirm Timezone. Auto-detect follows this computer; choose a named zone when the routine should follow a different office clock.
2. Open the Bot, choose View conversation details, then open Routines and select the routine.
3. Open When to run and add a schedule. Choices are Every hour, Every day, Weekdays, Every week, Every month, Interval, Advanced, and Custom. Weekdays means Monday through Friday. The clock time uses the Bot Timezone above, not the timezone of the website or Slack workspace the routine reads.
4. Save the routine. Saving does not run it. A schedule waits for the next matching time — if you save "every day at 8:00 AM" at 8:05, today's 8:00 run does not happen, and the first run is the next 8:00 AM in that timezone.
5. Turn Active on. An inactive routine stays saved and does not fire. If Grok Bot says schedules must be at least five minutes apart, widen the interval. Enter a valid schedule means the custom text is not a schedule Grok Bot can run.

A Bot can own up to 50 routines, and Run history keeps the 20 most recent runs. Right-click a run and choose Copy request ID when you need to escalate a failed fire.

After the first scheduled fire

Open Run history once the next matching time has passed. No runs yet means the panel has no run record — saving alone never creates one. Each run spends usage, so an hourly schedule or a short interval can burn a week of usage in a day; widen the cadence or pause unused routines before you raise a plan. Re-test after a website, connector, or source format changes. Deleting a routine is immediate with no undo.

Pitfalls

Expecting a save at 8:05 to catch today's 8:00 slot fails — the first fire is the next match. Leaving Active off keeps the routine saved while nothing runs. Using the Slack workspace timezone instead of Settings → Bot → Timezone shifts the clock silently. Stacking hourly schedules without checking Weekly usage drains the pool faster than a daily brief.