Cursor incident
Grok Bot routines not triggering
Resolved after under 1 min.
- Started
- Ended
- Worst state
- Partial outage
- On Cursor’s status page
- Source
- Components
- Grok Bot
Timeline
- Cursor status page · Resolved Between 10:52 AM and 1:29 PM PT on October 13, many Grok Bot routines started by webhooks, Slack, git, email and Linear events didn't run. Webhook callers may have seen an HTTP 400 "Automation run rate limit exceeded" error, and other triggers failed without an error. Your own usage didn't cause this. Routines are running normally again. Events sent during this window weren't processed and won't be retried automatically, so please resend anything important.
- Cursor status page · Reported Grok Bot routines not triggering
Cite this incident
Site Qwality, “Grok Bot routines not triggering,” Oct 13, 2026, https://siteqwality.com/is-cursor-down/incidents/cursor-202610132113/
Free to quote with a link to this page.