# Cursor: Grok Bot routines not triggering

- Impact (vendor’s label): major
- Status: resolved
- Started: 2026-10-13 21:13 UTC · Resolved: 2026-10-13 20:29 UTC · Duration: -44 min
- Updates: 1
- [Vendor status page: https://stspg.io/6x4hzfm1n6v7](https://stspg.io/6x4hzfm1n6v7)
- [Company: Cursor](https://rewindex.com/company/cursor.md)

## 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, sol)_
## Timeline of updates

- **resolved** 2026-10-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.

## Rewindex changes for this incident

- 2026-10-13 21:13 UTC: [Major incident: Grok Bot routines not triggering](https://rewindex.com/change/if3fc05ba466522.md)


---
Canonical: https://rewindex.com/company/cursor/incidents/bg1b759jsjqf · Markdown: https://rewindex.com/company/cursor/incidents/bg1b759jsjqf.md · JSON: https://rewindex.com/api/v1/companies/cursor/incidents/bg1b759jsjqf · Generated 2026-10-18T09:36:18.420Z