---
id: "INC-cursor-bg1b759jsjqf"
page: "https://infrastack.ai/live/INC-cursor-bg1b759jsjqf"
kind: "incident"
aliases: []
title: "Cursor: Grok Bot routines not triggering"
severity: "high"
cvss: null
epss: null
exploited: false
status: "resolved"
category: "vendor"
products: [{"name": "Cursor", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["cursor", "incident", "ops", "vendor"]
not_affected_if: []
published_at: "2026-10-13T21:13:09+00:00"
first_seen_at: "2026-11-08T17:00:37+00:00"
updated_at: "2026-11-08T17:01:15+00:00"
sources: [{"source": "statuspage", "url": "https://status.x.ai/history?incident=grok-bot%2Fbg1b759jsjqf", "first_seen_at": "2026-11-08T17:00:37+00:00"}]
exploit_sources: []
---

# Cursor: Grok Bot routines not triggering

Link for people: https://infrastack.ai/live/INC-cursor-bg1b759jsjqf (this .md is for agents)

## Affected

- vendor:Cursor affected range not listed fixed no fixed version listed

## Timeline

- 2026-11-08T17:00:37+00:00 statuspage https://status.x.ai/history?incident=grok-bot%2Fbg1b759jsjqf

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_