Cursor · 2h ago
Grok Bot routines not triggering
ResolvedYes — Cursor had a problem on October 13, 2026, and Cursor has since marked it resolved. Cursor's latest word: “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
Started: 10/13/2026, 9:13:09 PM
Last update: 10/13/2026, 9:13:09 PM
Resolved: 10/13/2026, 8:29:00 PM
Updates
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.
10/13/2026, 9:13:09 PM
More Cursor incidents
- Degraded performance and errors across Cursor services — resolved, 23h ago
- Investigating service degradation — Cloud Agents and Grok Bot — resolved, 4d ago
- Investigating service degradation — Cloud Agents — resolved, 4d ago
- Elevated errors affecting Opus 5.5 — resolved, 5d ago
- Opus 5.5 is Experiencing 429s — resolved, 5d ago
- Investigating service degradation — Grok Bot — resolved, 6d ago