Incidentsby IbisGrok Bot routines not triggering
Oct 13, 21:13 UTCOct 13, 20:29 UTC
Duration
0m
Impact
Major
Root cause
Not disclosed
Cursor, 90 days
88 incidents
Affected
Not listed by the vendor.
Final update
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.
Timeline
- Resolved · Oct 13, 20:29 UTC
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.
More from Cursor
Full historyDegraded performance and errors across Cursor serviceslasted 2h 46mInvestigating service degradation , Cloud Agents and Grok Botlasted 31mInvestigating service degradation , Cloud Agentslasted 12mElevated errors affecting Opus 5.5lasted 58mOpus 5.5 is Experiencing 429slasted 1h 37mInvestigating service degradation , Grok Botlasted 1h 26m