Cursor Status · History · Incident #148079
RESOLVEDGrok Bot routines not triggering
Major · Started Oct 13, 2026 · 8:29 PM
Cursor Status · History · Incident #148079
RESOLVEDMajor · Started Oct 13, 2026 · 8:29 PM
Duration
< 1m
Severity
Major
Detection lead
—
User reports
—
Summary
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.
Started
Oct 13, 2026 · 8:29 PM
Resolved
Oct 13, 2026 · 8:29 PM
Duration
< 1m
Severity
Major
Event timeline
Resolved
Oct 13 · 9:13 PM CursorBetween 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.
Pattern
Add it as a dependency monitor. The Free plan includes one.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.