Fix · Routines

Grok Bot routines not running

A routine never fires, fires at the wrong time, or shows Failed. Work the list top to bottom; the cheapest checks come first.

~5 min·Checked against the official docs 2026-10-31

1. ✓Mark step 1 as done

   1. Check the routine isn't paused

   On desktop, click the Bot's name at the top of the chat and open the Details tab. Each routine row shows when it runs, or Paused; use the switch on the row to resume it. On the phone, open the Bot's profile, tap the routine and make sure Active is on.

   Why it happens: Pausing is silent. A paused routine shows no error; it simply doesn't start. Grok Bot can also pause routines itself after a long period away if you don't answer its check-in.
2. ✓Mark step 2 as done

   2. Read “When to run”, including the time zone

   Open the routine and read When to run, which shows the saved schedule in words. If it doesn't match what you meant, choose Edit and tell the Bot what to fix.

   Schedules use the time zone in Settings → Bot → Timezone. Auto-detect follows the computer you're on, so pick a zone explicitly when the routine should follow a different one.

3. ✓Mark step 3 as done

   3. Remember a new schedule waits for its next time

   A new routine doesn't run when it's created. If you set up “every day at 8:00 AM” at 8:05, the first run is tomorrow at 8:00 AM. To run it now, open the routine on desktop and choose Test. A test performs real work, so use a safe input.

4. ✓Mark step 4 as done

   4. Read the run history

   On the phone, the routine's Run history shows each recent run as Running, Succeeded or Failed, with the reason for a failed run. No runs yet means nothing has started it. Only the 20 most recent runs are kept.

   Why it happens: A run that “did nothing” may have succeeded. A well-written routine stays quiet when there's nothing new, so check the history before assuming it didn't fire.
5. ✓Mark step 5 as done

   5. Check the apps it needs are still connected

   The routine depends on its apps staying signed in and on the computer reaching the source system. Open Connect apps and look for Needs auth or Disconnected on anything the routine uses, then choose Authenticate. Also confirm the owning Bot still exists: deleting a Bot removes its routines. If an app keeps dropping, use the connector fix.

6. ✓Mark step 6 as done

   6. Check rate limits and usage

   All your routines together can run up to 300 times an hour, and each routine up to 200 times an hour. A run past either limit fails with Automation run rate limit exceeded and isn't retried automatically, so rerun it with Test (or resend the webhook call). The docs note some runs can fail with this error because of a limit all Grok Bot routines share, a known issue being fixed.

   Each run also spends usage. If your weekly usage is used up, or your account access is paused, routines stop too. See the usage-limit fix.

7. ✓Mark step 7 as done

   7. For event-triggered routines, check the trigger

   For a Slack trigger, the message has to be new, in the channel the trigger watches, and match its phrase. Events from before the trigger existed don't count, and the Slack trigger is separate from the Slack app, so Slack must be connected on the Cursor account that owns the Bot. For a webhook, the call must return 200 and use the current key; any other response means no run started.

8. ✓Mark step 8 as done

   8. Rule out an outage

   If several routines stopped at once, check whether Grok Bot is having an incident on our status page or the official one. During an incident, wait; don't reset the computer.