Read When to run after every routine edit

How this helps you

You catch schedule typos before they multiply usage overnight.

Create a routine on this Bot only: [schedule_or_event]. Instruction: [job]. After you save it, quote back the exact When to run and Instruction text. Do not create any other routines. Ask me before enabling a listener on all Slack messages.

What they did

GrokBot Guru's bots narrate official routine behaviour: ask the owning Bot in plain words, schedules follow the Bot time zone, a routine created at 8:05 for "every day at 8:00" first runs tomorrow, Slack and webhook events need narrow filters, and When to run is written in words on the Details tab. Hail warns that if it says every hour and you meant every day, you just bought 24x the runs. Test does real work. Brand-new low-traction video, kept because the checklist is unusually clear for advanced triggers.

Who it's for: Anyone creating schedule or event routines after the Nov usage squeeze.

Before you start

• At least one Bot you can open on desktop
• A routine you already created or are about to create

How to try it

1. Ask the Bot that should own the job: what to do and when, in plain words.
2. Open the Bot name at the top of chat, Details tab, Routines, and open the new routine.
3. Read Instruction and When to run out loud; confirm time zone under Bot settings.
4. If wrong, choose Edit, send the correction in chat, then read When to run again.
5. Run Test only with a safe input; remember it can change files and connected apps.
6. For Slack events, limit to one channel plus a phrase; for webhooks, treat HTTP 200 as accepted, not finished.

What to expect

You meant a daily 9am support digest; When to run showed every hour; you edit once and save a day of usage.

Common mistakes

• Assuming a routine created just after its clock time already ran.
• Listening to every Slack message in the workspace.
• Treating a webhook 200 as job complete.

Related tips

• Make routines cheaper: events, slow schedules, change checks: A 5-minute routine wakes 8,640 times a month. Use an event trigger, the slowest schedule that works, and a cheap change check.
• Put quiet hours inside the routine itself: Have the routine re-check the clock right before it acts, and skip itself if it's too late.
• Create a routine by asking, then ask what else to schedule: Describe a schedule in one sentence to make a routine, then ask the Bot which routines it thinks you need.

Worth knowingYou catch schedule typos before they multiply usage overnight.

Learn more: Grok Bot Routines Not Working? Do It by Hand, Save a Skill, Then Schedule · All Grok Bot routines tips