Grok BotGuide

Routines

Grok Bot routine did not run

A Grok Bot routine did not run because it is disabled, the schedule or time zone is wrong, usage is paused, or the run sat in a queue. Deleting the routine is not the first fix.

Staff say a label of Next run: Run now often means the slot already fired and waited, sometimes 10 to 37 minutes. Some runs finish without posting anything in chat.

Skills first, then routines

Why the native method fails

The native method is to delete the routine and create it again, or to rewrite the bot's instructions, because the clock looks stuck. Staff say editing bot instructions, or which platform created the routine, does not break the schedule. Recreating it throws away the run history you would have used to see the failure. A routine that came due while weekly usage was blocked was skipped. It does not queue up and run later as a surprise send when the meter refills. Creating a twin routine will not replay the skipped slot.

Steps

  1. Open the routine. Official troubleshooting says to verify that it is enabled, that the schedule and time zone are correct, that the owning bot still exists, that required plugins are still authenticated, that the computer can reach the source system, and that usage or account access is not paused.
  2. Read recent run history before you edit anything. If the history shows a run that finished with no chat line, that matches the staff note: some runs complete without posting. Message the bot and ask for an on-demand check-in instead of rebuilding the schedule.
  3. If the label says Next run: Run now for a long time, wait through the queue window staff described, on the order of 10 to 37 minutes, before you call it dead. Do not recreate the routine while that wait is the documented behavior.
  4. Use Test run only with safe input. Official warning: tests do real things. They can navigate sites, change files, and call connected tools. Put write actions behind approval.
  5. For an event trigger, confirm the source channel, repository, and matching rule are still valid. Event triggers come from Cursor account integrations. That path is not the same authorization as the Slack or GitHub plugin, and it may need to be granted separately. A narrow rule matters: every new message burns usage and acts on mail you did not mean.

Limits

The webhook URL and the sender key for a webhook routine appear only on the desktop app, not on iOS. Open the trigger card on the desktop. Updating the phone will not reveal that URL.

The product cap recorded in the skills lesson is 50 routines per bot, and the app keeps the latest 20 runs per routine. Deletes take effect immediately and have no undo. Deleting a bot deletes its routines. After a long absence the product may ask whether to keep routines running. No answer pauses them. That pause is not a failed cron on your laptop. Background routines can run with the laptop closed. Idle sleep of the cloud computer, which kills background processes and can drop installed packages, is a separate fact about the machine. Do not confuse a sleeping package daemon with a skipped routine unless the run history says the routine itself failed.

A webhook POST that returned an internal error was a server-side rollback in one staff thread. The same request worked after they reverted the change. If your routine's history shows that class of error, write support with the time. Recreating the routine does not roll back their API.

FAQ

Next run says Run now for half an hour. Is the schedule broken?

Staff say the slot often fired and sat in a queue, commonly 10 to 37 minutes. Some finished runs never post to chat. Check history, then message the bot, before you delete the routine.

I edited the bot instructions. Did that clear the schedule?

Staff say editing instructions, or which platform created the routine, does not break the schedule.

The weekly meter was full overnight. Will this morning replay every skipped run?

No. Routines that came due during the block were skipped. They do not run later as a batch. Messages you sent by hand during the block are the ones that reply in a batch.

Where is the webhook URL on my iPhone?

Nowhere. Staff say the POST URL and sender key appear only on the desktop app.

Can I test a routine that sends mail?

Only if you accept that Test run performs real actions. Official docs say to use safe inputs and to keep writes behind approval.

Related

Sources

  • Official troubleshooting
  • Routines sit in a queue
  • Webhook URL is desktop-only
  • Webhook server error