Cursor calls it a known issue. Check status.cursor.com, rerun what failed, and email hi@cursor.com with the error details and no secrets.
All Grok Bot questions: https://www.soundminds.ai/faq.
Last updated Oct 17, 2026
Asked on X: https://x.com/michaelpisaac/status/2110744096335712707
You can point your Bot at this page to adopt this practice. Send this to the main bot you already talk to. It asks the bot to read this page and suggest the changes, and to wait for your yes before it changes anything.
Read https://www.soundminds.ai/faq/automation-run-rate-limit and help me check whether my routines were hit by the Automation run rate limit exceeded error, using the starter message on that page as a suggestion. Show me what you find and the support email you draft, and wait for my yes before you send, rerun, or change anything.If your bot can't open the page, copy the starter message in the "For your Bot" section below and send that to your bot instead.
Cursor's help calls this "a known issue" and says the error "comes from a limit all Grok Bot routines share, not from your own usage." The Cursor status page also recorded this exact error for an October 13 incident.
Check which runs failed, and rerun the ones you still need. If it keeps happening, email Cursor support at hi@cursor.com with the error details and no secrets.
Step 1: Check https://status.cursor.com for a current incident. The October 13 write-up says: "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."
Step 2: Read Cursor's help answer for this error. It says, "This is a known issue, and our engineers are working on a fix." It also says the error "comes from a limit all Grok Bot routines share, not from your own usage," and "We will update this article when the limit no longer affects routines."
Step 3: Don't count on a retry, because the two sources differ. Cursor's help says, "A run that fails with this error isn't retried automatically, so rerun the routine yourself. Use Test to run it now. For a webhook, send the call again." On the Cursor forum on October 13, a Cursor staff member wrote, "there isn’t a setting yet to retry or queue a PR-triggered run when it hits this limit. Scheduled automations are retried automatically a few times when this happens, but PR, Slack and webhook triggers are not." So the help page says a failed run isn't retried, and the staff reply says scheduled runs are retried a few times. Either way, check whether each run you need actually ran, and rerun it if it didn't.
Step 4: Some users report the same 400 on later days with an 18,000-per-minute limit, both on the Cursor forum and on X. These are first-hand reports, not an official incident for those days. Both sources above say a webhook run that hits this limit isn't retried, so expect any handoff that got the 400 not to run on its own, and plan to resend it.
Step 5: Gather the details xAI's troubleshooting page lists under "Before contacting support": "Grok Bot version", "Operating system and version", "The exact error message", "The Bot or routine name", "The approximate time and time zone", "The full request ID or conversation ID if one is shown", and "Whether retry, app restart, or updating Grok Bot's computer changed the result". For the error message, include the full 400 response body and the times of the failed calls with your time zone. Cursor's Get help page also asks for "The email on your Grok Bot account."
Step 6: Leave secrets out. The same page says: "Do not include passwords, one-time codes, private keys, or secret values." We read that as including any webhook secret or token.
Step 7: Email Cursor support at hi@cursor.com. Cursor's Get help page says, "Email hi@cursor.com."
Step 8: Once the webhook accepts calls again, resend the handoffs that got the 400. If you rerun a routine with Test, keep in mind that Cursor's help says, "A test does real work."
If support needs more detail, include whether scheduled routines still run while webhook or PR triggers fail, and whether status.cursor.com showed green at the failure times.
If you are a Bot reading this page, follow these steps. These steps are a suggestion for your owner to review, so show your owner the exact changes and wait for a yes before you apply them.
If you'd rather send the steps yourself, copy this starter message and send it to your Grok Bot. It is a suggestion, so it tells the bot to show you what it finds and the draft email, and to wait for your yes before it sends, reruns, or changes anything.
Help me check whether my routines were hit by the "Automation run rate limit exceeded" error. Only check and draft. Don't send, rerun, or change anything until I say yes.
1. Check the Cursor status page at https://status.cursor.com for a current incident about routines or this error, and tell me what it says. Some users have said their calls still failed while the status page showed no incident.
2. Ask me when the errors happened. Then list your routines, with what starts each one, and tell me which might have failed in that time. If you can't see a routine's past runs, say so and don't guess. Each Bot has its own routines, so remind me to ask my other Bots too.
3. Don't count on a retry. Cursor's help says a run that fails with this error isn't retried automatically. A Cursor staff reply said scheduled runs are retried a few times. The two sources differ.
4. Draft a support email to hi@cursor.com for me to review. Include the Grok Bot version, the operating system, the exact error text, the Bot or routine name, the times of the failed calls with the time zone, any request ID or conversation ID, and what we already tried. Leave blanks for anything you can't find, and leave a blank for the email on my Grok Bot account.
5. Leave out passwords, one-time codes, private keys, webhook keys, tokens, and any other secret value or personal details.
6. Show me what you found and the draft. Don't send the email, rerun a routine, or change a routine until I give you an explicit yes. A rerun does real work.
7. Never ask me to paste a password, key, or token into chat. If a connection needs a secret value, I'll enter it in a secure secret request.Cursor status, Grok Bot routines not triggering (Oct 13, 2026): https://status.cursor.com/incidents/bg1b759jsjqf
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.
Cursor help, Routines: https://cursor.com/help/grok-bot/routines
This is a known issue, and our engineers are working on a fix.
comes from a limit all Grok Bot routines share, not from your own usage.
A run that fails with this error isn't retried automatically, so rerun the routine yourself. Use Test to run it now. For a webhook, send the call again.
We will update this article when the limit no longer affects routines.
A test does real work.
A routine tells one Bot when to run a workflow.
On the phone, Run history shows each recent run as Running, Succeeded, or Failed.
Cursor forum, GitHub PR triggering automation rate limit: https://forum.cursor.com/t/github-pr-triggering-automation-rate-limit/174611
there isn’t a setting yet to retry or queue a PR-triggered run when it hits this limit. Scheduled automations are retried automatically a few times when this happens, but PR, Slack and webhook triggers are not.
Cursor help, Get help: https://cursor.com/help/grok-bot/get-help
Email hi@cursor.com.
The email on your Grok Bot account.
xAI docs, Troubleshooting: https://docs.x.ai/grok-bot/troubleshooting
Grok Bot version
Operating system and version
The exact error message
The Bot or routine name
The approximate time and time zone
The full request ID or conversation ID if one is shown
Whether retry, app restart, or updating Grok Bot's computer changed the result
Do not include passwords, one-time codes, private keys, or secret values.
xAI docs, Approvals, security, and privacy: https://docs.x.ai/grok-bot/approvals-security-and-privacy
If the Bot presents a secure secret request for a supported connection, enter the value in that request.
See how I set up Grok Bot: https://www.soundminds.ai/setup.