Incidente di Cursor
Grok Bot routines not triggering
Risolto dopo meno di 1 min.
- Inizio
- Fine
- Stato peggiore
- Disservizio parziale
- Sulla pagina di stato di Cursor
- Fonte
- Componenti
- Grok Bot
Cronologia
- Pagina di stato di Cursor · Risolto 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.
- Pagina di stato di Cursor · Reported Grok Bot routines not triggering
Cita questo incidente
Site Qwality, “Grok Bot routines not triggering,” 13 ott 2026, https://siteqwality.com/is-cursor-down/incidents/cursor-202610132113/
Puoi citarlo liberamente con un link a questa pagina.