Fix a Grok Bot routine that did not run

When a scheduled or event-triggered routine stays silent, official troubleshooting starts with the routine itself. Creating a routine is covered in Save a Grok Bot skill and schedule a routine. This page is the miss checklist.

Check the routine

Open the Bot → View conversation details → Routines, then open the routine that should have fired. Verify each item:

1. It is enabled (not paused).
2. The schedule and time zone are correct for when you expected the run.
3. The owning Bot still exists.
4. Required plugins remain authenticated.
5. The computer can reach the source system the routine needs.
6. Usage or account access has not been paused.

Inspect recent run history for a failure message.

Event listeners

For a Slack, GitHub, or other event-triggered routine, also confirm:

1. The source channel, repository, or matching rule is still valid.
2. The Cursor Slack app is invited to that channel when the listener is channel-scoped.
3. The match is narrow enough that the event you care about still qualifies.

Test without guessing

Use Test run only with safe input. A test run performs real external actions: it can open sites, change files, and call tools. Prefer a dry target before you re-arm a production send.

After a long stretch away, answer the keep-running prompt when Grok Bot asks. Hiding a Bot from the sidebar does not pause its routines; a paused routine does.

Pitfalls

• Usage pause and “Bot failed to respond” are separate from a disabled schedule. See Understand Grok Bot usage and “Bot failed to respond”.
• If the cloud computer is unreachable, fix reachability first: Fix Grok Bot “Can’t reach your computer”.
• Deleting the Bot deletes its routines. There is no undo on routine delete.