Why a Grok Bot routine runs late, and how to design around it

A routine that "did not run" usually did. It fired on time and then waited.

Late, not never

Scheduled runs across Grok Bot wait in a shared queue before they start. Staff described runs starting 10 to 45 minutes late at busy hours, worst around 5 to 9 AM US Pacific. One user's 13:15 handoff looked stuck at 13:42 and had in fact only started at 13:37. A Next run field showing Run now is that queued state.

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

Open the Bot, then Details, the routine, Run history. The app keeps the 20 most recent runs per routine, so check soon.

If it really did not run

Work through the routine itself:

Is it enabled, not paused? The app may pause routines after a long absence and ask you to confirm.
Are 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 its plugins authenticated, and is your usage paused or a spending limit reached?
For event triggers: are the source channel, repository and matching rule still valid?

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

Platform incidents

On October 8, 2026 scheduled routines 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. A backup routine 15 minutes later was held too. If many people report the same thing the same day, ask the Bot to run the job manually and leave the routine on.

Tools that only work in chat

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

Design for delay

Never rely on an exact-minute start. Allow a margin.
Make the routine idempotent: "process everything since the last successful run", not "process the last 30 minutes".
Prefer fewer, wider-spaced routines. They also cost less, as covered in Cutting Grok Bot usage without losing capability.
Know which tool you want: a skill is the saved method, a routine is when to run it. See Skills, routines, templates and memory.