Changes / Cursor / Grok Bot routines not triggering
Cursor: Major incident: Grok Bot routines not triggering
Summary
A major outage prevented many Grok Bot routines triggered by webhooks, Slack, git, email and Linear events from running; missed events won't be retried automatically. Service recovered, but recorded timestamps conflict: started 2026-10-13 21:13 UTC, resolved 2026-10-13 20:29 UTC; duration unknown.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Grok Bot routines not triggering
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-10-13 21:13 UTC
Before: not present
After: 2026-10-13 20:29 UTC
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Grok Bot routines not triggering (this change) A major outage prevented many Grok Bot routines triggered by webhooks, Slack, git, email and Linear events from running; missed events won't be retried automatically. Service recovered, but recorded timestamps conflict: started 2026-10-13 21:13 UTC, resolved 2026-10-13 20:29 UTC; duration unknown. | Major incident |