Why didn't my Grok Bot routine run on time?

1. Check whether it ran late, not never

Open the Bot → Details tab → the routine → Run history. The app keeps the 20 most recent runs per routine.

Forum staff explained that scheduled runs across Grok Bot wait in a queue before they start. A 13:15 handoff that "was still thinking at 13:42" had in fact only started at 13:37. A Next run field showing Run now is that queued state. In September 2026 staff changed queueing to reserve a slot a few minutes out, which removed silent skips, but runs can still start a few minutes late at the busiest hours.

A direct message to the Bot skips the queue, which is why "wake up" messages always seemed to work.

2. Check the routine itself

• Is it enabled, not paused? Hiding a Bot does not pause its routines, but the app may pause routines after a long absence and ask you to confirm.
• Is the schedule and time zone right? Ask the Bot to show the cron line and time zone.
• Does the Bot still exist? Deleting a Bot deletes its routines.
• Are the plugins it needs authenticated? Is your usage paused or a spending limit reached?
• For event triggers: is the source channel, repo and matching rule still valid?

Use Test only with safe input — test runs perform real actions.

3. Was it a platform incident?

On October 8, 2026, scheduled routines across Grok Bot were held back and marked Failed during very high load, while direct messages kept working. Staff said pausing, copying or recreating routines would not help, and that missed runs are not replayed automatically. A backup routine 15 minutes later did not help either; both were held.

If many people report the same thing on the same day, ask the Bot to run the routine manually and leave the routine switched on.

4. Tools that only work in chat

As of October 2026, scheduled routine runs do not get the Bot's own inbox tools (mail sent from its claimed address) or, reported later, phone calendar tools — chat turns do. If your routine "falls back to Gmail" or says a tool was not found, that is why. Send through a plugin such as Gmail, or have the routine hand the step to the Bot's main chat for approval.

Designing routines that survive delays

• Do not rely on exact-minute starts. Allow a margin.
• Make the routine idempotent: "process everything since the last successful run", not "process the last 30 minutes".
• Fewer, wider-spaced routines also cost less. See Why does Grok Bot use up my weekly usage so fast?