Fixes / Routines
Routine paused for inactivity
Routines that haven't run in a while get paused automatically. What counts as inactivity, how to resume, and how to structure low-frequency work so it doesn't get shelved.
Short answerGrok Bot pauses long-inactive routines. Resume it, then change its shape: give trigger-only routines a light scheduled heartbeat run, or fold rare tasks into a daily routine that checks whether they're due.
What's happening
The docs note that long-inactive routines are paused automatically. This mostly catches event-triggered routines (a Slack mention, a GitHub notification) that simply haven't been triggered, and monthly tasks.
Resume
Open the Bot → Routines → the routine → resume. Check the run records to confirm the last successful run.
Restructure so it doesn't recur
- Heartbeat. Give the routine a daily scheduled run whose instruction is "check whether the trigger condition occurred since last run; if not, log 'no-op' and stop." It stays active and costs almost nothing.
- Fold monthly into daily. A daily "ops" routine that reads a small calendar file of due tasks and runs the ones due today. One always-active routine instead of twelve rarely-active ones.
- Limits to know. A Bot can own up to 50 routines and keeps the 20 most recent run records per routine. Fewer, better-shaped routines are easier to keep alive.
Verified 28 Aug 2026 · Facts about Grok Bot change during beta. See changelog.