Run the official checklist first

The official troubleshooting entry for a routine that did not run lists the things to verify before anything else. Most missed runs come down to one of these.

Documentation: Official troubleshooting ↗

  • The routine is enabled, not just saved.
  • The schedule and time zone are what you intended.
  • The Bot that owns the routine still exists and was not deleted or recreated.
  • Every plugin the routine needs is still authenticated.
  • The shared computer is reachable; a stuck computer silently skips scheduled work.
  • Your account still has access and allowance; an exhausted allowance with on-demand disabled stops routines.

The limits that look like bugs

Two documented numbers explain a lot of confusion. A Bot can own up to 50 routines, and only the 20 most recent run records are kept per routine. If you inspect history after a busy routine has run more than twenty times, earlier runs are simply gone. Keep your own log for anything you need to audit.

The docs also say Grok Bot may ask whether to keep routines running after a long period away and pause them if there is no response. People who set up a routine and then stop opening the app find it paused, not broken. Open the app periodically or expect that prompt.

Routine management still leans on desktop: the mobile guide says editing schedules and test runs require the desktop app.

Documentation: Skills and routines ↗

Schedules that never fire

A forum thread with 15 replies reports routines that do not auto-run on schedule despite being enabled. The reports cluster around the August computer incident and around Bots whose computer was reset after the routine was created. If the checklist passes and the routine still skips, recreate it on desktop, run it once manually with a safe input to confirm the owning Bot and plugins work, and then re-enable the schedule.

Documentation: Forum: routines don't auto-run on schedule ↗ Official troubleshooting ↗

  1. Open the routine and confirm enabled, schedule, and time zone.
  2. Run it manually with a harmless input and watch the computer view.
  3. If the manual run works, re-save the schedule and wait for the next tick.
  4. If it still skips, recreate the routine on desktop and note the app version.

Webhook routines with no POST URL

Event routines can be triggered by integrations such as Slack messages or GitHub notifications, and by a webhook. A 29-reply thread describes the desktop app on Windows 0.47.0 showing no POST URL and no key for a webhook routine, so nothing external can call it. Update to the latest build, recreate the routine, and if the fields are still blank, report it in that thread rather than trying to guess a URL.

Documentation: Forum: webhook routine shows no POST URL (Windows 0.47.0) ↗ Skills and routines ↗

Write routines that fail loudly

The official guidance recommends a no-data and stale-data policy for every routine: say what should happen when a source is missing. The example is 'If the source data is unavailable, report the failure instead of using old data.' A routine that reports a failure is one you notice; a routine that quietly reuses yesterday's numbers is one you discover weeks later.

Documentation: Skills and routines ↗

Try this brief

Every weekday at 8:00 AM in my time zone, open the attached tracker and produce a five-line summary of changes since the last run. If the tracker is unreachable, empty, or unchanged, send a one-line message saying so and do not reuse a previous summary. Do not edit the tracker. Return the summary for my review.

Original editorial template. Replace placeholders and review access before running.

Quick answers

How many routines can a Bot have?

The official docs say a Bot can own up to 50 routines, and the app keeps the 20 most recent run records for each routine. Older runs disappear from history, which can look like the routine never ran.

Why did my routines pause on their own?

The docs say Grok Bot may ask whether to keep routines running after a long period away, and pause them if there is no response. If you have been away from the app, open it and answer that prompt before assuming a bug.

My webhook routine shows no POST URL. Is that normal?

No. A Windows 0.47.0 forum thread with 29 replies describes exactly this. Update the app, recreate the routine on desktop, and if the URL and key still do not appear, add your version to that thread; it is a known report, not a configuration mistake.

Sources & next steps

Capabilities are grounded in the documentation below. The workflow design and acceptance checks are editorial suggestions.

Build your own workflow brief ↗