Grok Bot routines were held back again Tuesday morning
Staff say scheduled routines are flowing again since about noon ET, but runs missed this morning won't be replayed.
If a Grok Bot routine was due this morning, check its run history and run it by hand if it was skipped. Cursor staff member kevinn said at 3:36 PM ET on Oct 13 that "Earlier today (Tuesday morning, US time), routines were being held back again for a few hours." He added that "Runs missed during these windows won't be replayed automatically."
- Status: Resolved for the morning window, per staff. Late starts at busy times are still a tracked issue.
- Window: Tuesday morning US time, for "a few hours." Routines have been going through since about 16:00 UTC, which is 12:00 PM ET.
- Symptoms: Scheduled runs started late or never fired. One user said at 3:08 PM ET that "all routines are over an hour late or just never fired."
- Workaround: Run the missed task yourself by messaging the Bot.
What changed#
This is a repeat of the routine delays that started on Oct 8. kevinn said on Oct 13 that the first issue "was resolved on October 9," and that today's hold has "also been resolved." There was no incident for it on status.cursor.com when we checked at 4:14 PM ET. The most recent incident listed there ended at 11:07 PM ET on Oct 12.
Update, Oct 13: At 5:13 PM ET, Cursor posted a resolved incident, "Grok Bot routines not triggering", for 1:52 to 4:29 PM ET. It covers routines started by webhooks, Slack, git, email and Linear, not this morning's scheduled hold, which still has no status entry. If you also use event triggers, resend anything from that afternoon window: [[entry:status-routines-not-triggering-oct-13]].
Why it matters#
Morning routines are often the ones people depend on most, such as inbox triage, digests and briefings. Since missed runs aren't replayed, anything due this morning may simply not exist today unless you start it.
How to use it#
- Open each routine that was due before noon ET and check whether today's run happened.
- For any that didn't, message the Bot and ask it to run the task now. For example:
My "Morning brief" routine didn't run this morning. Run it now and send me the result here.
- If you paused, deleted or recreated routines while troubleshooting, kevinn asked you to "check that the ones you want are switched back on."
- If a routine still fails outright after today, kevinn asked people to reply in the forum thread "with the routine name and the time it was due."
Good to know#
- Late starts aren't fully fixed. kevinn said "During busy periods, some routines may still start later than their scheduled time. This is an issue we're tracking."
- Gmail forwarding to a Bot's inbox and Cursor Automations problems are separate issues, according to kevinn, who asked those users to open new threads.
What to watch#
Whether the late-start problem at busy times gets a fix or a status page entry, and whether missed runs ever get an option to replay.
