How do I schedule Grok Bot routines?
In the conversation with the Bot that owns the job, say when it should run, what it should do, what to deliver and what to do if data is missing. The Bot repeats the settings for you to confirm, creates the routine and shows the next run. Set the time zone under Settings → General → Bot → Timezone.
Recommended order
Section titled “Recommended order”The official advice: do the task once by hand, refine it, save it as a skill, and only then automate it with a routine. Scheduling an untested workflow makes failures hard to debug.
Six things to state
Section titled “Six things to state”The Bot confirms these before creating the routine, so give them up front:
- The owning Bot
- The schedule and time zone
- The input source
- The expected result
- The approval boundary
- What to do when a source is missing
For example: “Every weekday at 8:00 (America/New_York), run the Daily customer-risk skill on the current account list and post a linked watch list here. Do not contact customers. If a source is unavailable, report a failure instead of using old data.”
Managing routines
Section titled “Managing routines”Open the Bot → View conversation details → Routines to enable or pause, run a Test run, edit the schedule or instruction, review recent runs, or delete. A Test run does real work, so use safe inputs. On mobile you can view history, pause and resume, but not edit schedules or test.
Limits
Section titled “Limits”| Item | Limit |
|---|---|
| Routines per Bot | Up to 50 |
| Run history kept | 20 most recent per routine |
| Minimum interval | 5 minutes |
| Deleting | Immediate and permanent; deleting a Bot deletes its routines |
Event triggers
Section titled “Event triggers”Besides schedules, Cursor account integrations can start a routine from events such as Slack messages or GitHub notifications. Keep matching rules narrow, such as one channel plus one phrase, rather than every new message.
Routine did not run?
Section titled “Routine did not run?”Check the official list:
- The routine is enabled
- The schedule and time zone are correct
- The owning Bot still exists
- Required plugins are still authenticated
- The computer can reach the source system
- Usage or account access has not been paused
After a long absence Grok Bot may ask whether to keep routines running; if you do not answer, they may be paused.
Do not schedule too often
Section titled “Do not schedule too often”Every run uses usage even when nothing changed. Flavio Copes points out that every 15 minutes is 96 runs a day.
Related questions
Section titled “Related questions”How often can a Grok Bot routine run?
Section titled “How often can a Grok Bot routine run?”Routine schedules must be at least five minutes apart.
Do routines run when my laptop is closed?
Section titled “Do routines run when my laptop is closed?”Yes. Routines run on Grok Bot’s cloud computer, so closing your laptop or the app does not stop them.
Which time zone do routines use?
Section titled “Which time zone do routines use?”The Timezone set under Settings → General → Bot.
Read next
Section titled “Read next”Continue with a complete tutorial
Browse all 25 complete tutorials →Start with original practice inputs, follow the staged prompts, then compare the complete reference results and acceptance checks. Each tutorial states what was tested and what still needs validation.
- Gmail inbox organization: labels, drafts and a daily brief8 synthetic emails, 6 labels plus Review, a classification table, reply drafts and a daily brief with staged acceptance.5 stages · 7 prompts · 5 files
- Website checks: three fixture faults and a reproducible reportInspect page status, links, images and anchors on an intentionally faulty training site. Keep findings, impact and repairs separate before arranging recurring checks.6 stages · 6 prompts · 7 files
References are listed below, but no documentation review date is recorded: unverified. If the interface looks different, send feedback or edit the page.Send feedbackEdit this page