A routine stopped running
A routine that ran fine last week silently stopped. Inactivity pause, connector expiry, plan change, update regression, a stuck approval, or the Bot decided it was done. Check in this order.
The six causes
1. Inactivity pause. Long-inactive routines are paused automatically. If it hadn't done anything for a while (say a routine that only acts when a trigger fires), it may have been shelved. Open the routine, check its status, resume.
2. Connector expired. OAuth tokens expire; a password changed on the Bot's account; a tool revoked access after a security event. The run record will show a failed step early. Re-authorise as the Bot user.
3. Plan or allowance. Allowance exhausted and on-demand off means routines stop. Plan downgraded means Bots may be unavailable. Check the dashboard.
4. Update regression. Grok Bot ships weekly. A change in how the browser, a plugin, or delegation works can break a routine that hasn't changed. Check our changelog and re-test the routine manually.
5. Stuck approval. The routine reached a step needing your approval and you didn't see the notification. Approvals pile up. See approvals piling up.
6. The Bot decided. Instructions like "until the backlog is clear" can be satisfied. The Bot marks the job done and the routine does nothing. Rewrite with a cadence.
Prevention
A heartbeat: every routine writes one line to a log file when it completes. A daily watcher routine reads the log and reports any routine that hasn't written in its expected window. Cost: near zero. Silent failures: gone.
Verified 28 Aug 2026 · Facts about Grok Bot change during beta. See changelog.