Cursor automations hit a platform-wide start limit for hours today
PR, Slack and webhook runs blocked by the limit were dropped, not retried. Here is how to find and re-fire them.
If a Cursor automation on a pull request, Slack, or webhook trigger didn't run today, check its Runs list and re-fire anything that failed. On Oct 13 at 12:36 PM ET, Cursor staff member kevinn said the failed runs "were blocked by a platform-wide limit on how many automation runs can start per minute across all customers." He said the limit "was saturated for several hours today and has since cleared."
What changed#
Phil_Waters reported that an automation triggered by pushes to a PR was being rate limited, and that the run "appears to fail silently and isn't retried." kevinn confirmed the cause was the shared limit, "not by anything your team did," and said new pushes "should be going through normally again." status.cursor.com showed no incident for it when we checked at 12:38 PM ET.
Update, Oct 13: At 5:13 PM ET, Cursor posted a resolved status incident, "Grok Bot routines not triggering", for 1:52 to 4:29 PM ET. It covers Grok Bot routines started by webhooks, Slack, git, email and Linear, with the same "Automation run rate limit exceeded" error, and says events in that window "won't be retried automatically, so please resend anything important." It doesn't name Cursor Automations, so there is still no status entry for this piece's PR-trigger failures. Details: [[entry:status-routines-not-triggering-oct-13]].
Why it matters#
Only some triggers get a second chance. kevinn said scheduled automations "are retried automatically a few times when this happens, but PR, Slack and webhook triggers are not." A review or test automation on a PR may have simply skipped today's pushes.
How to use it#
kevinn's recovery steps:
- Open the automation in the dashboard and check its Runs list.
- Look for runs marked failed with "rate-limited due to too many concurrent runs." Those are the PRs that were missed.
- Push a new commit to each affected PR to fire the trigger again. An empty commit works:
git commit --allow-empty -m "Re-run automation"
git push
- If the job can also run on a schedule (for example a periodic pass over open PRs), add one. Scheduled runs get the automatic retries.
Good to know#
- Status: Cleared, per staff. No start or end times given.
- There is no setting yet to retry or queue a PR-triggered run that hits the limit. kevinn passed the request for automatic retry or queuing to the team.
- Staff did not say whether Grok Bot routines with webhook triggers were affected. We have not seen reports of that.
- Update, Oct 13: They were. The 5:13 PM ET status incident confirms Grok Bot webhook routines failed from 1:52 to 4:29 PM ET.
- We could not re-test Cursor Automations from this box.
What to watch#
Whether Cursor adds retry or queuing for PR, Slack and webhook triggers, and whether a status page entry ever covers Cursor Automations as well as Grok Bot routines.
