Cursor Automations triggered by PR pushes fail silently and are not retried: `rate-limited due to too many concurrent runs` (platform-wide limit; re-fire with an empty commit)

Context

Source(s): https://forum.cursor.com/t/github-pr-triggering-automation-rate-limit/174611 Signal: 85 views; staff answer accepted (2026-10-13); the original poster did not report back after re-running, and the three later replies (2026-10-13 to 10-15) are about webhook-triggered routines in a different product, not Cursor PR triggers. Status: reported working by source, not reproduced by us (workaround only; root fix not confirmed).

Problem

An automation triggered by pushes to a pull request sometimes doesn't run. The run fails without a notification and is not retried, so someone has to notice the missed PR and start it again by hand.

Error (redacted / normalized)

rate-limited due to too many concurrent runs

Applies when

Cursor Automations (cloud agents) with a GitHub pull request push trigger, October 2026.

Confirm it is this problem

1. Open the automation in the Cursor dashboard and look at its Runs list (staff). → expect: the missed runs show as failed with the message above.

Not this when / boundary

Runs fail with a different message, or only your own runs fail while the platform is otherwise fine (our inference). Webhook calls refused with HTTP 400 Automation run rate limit exceeded, which three later replies reported for another product's webhook-triggered routines, are a different case with no fix in the thread.

Root cause

Per Cursor staff: a platform-wide limit on how many automation runs can start per minute across all customers was saturated for several hours on 2026-10-13; it was not caused by the team's own usage. Scheduled automations are retried automatically a few times when this happens, but PR, Slack and webhook triggers are not, and there is no setting yet to retry or queue them.

Fix

1. Find the PRs whose runs were dropped in the automation's Runs list (staff).
2. 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" and then git push (staff). → expect: a new run starts for that PR.
3. If the job can also run on a schedule (for example a periodic pass over open PRs), add a scheduled automation as a backstop, because scheduled runs get automatic retries (staff).

How to verify

The new run for the PR appears in the Runs list and completes instead of failing with the rate-limit message.

What did not work

None reported for PR-triggered automations; nobody reported back after the staff answer.

Risks

An empty commit adds a commit to the PR history; squash or drop it before merging if your team requires a clean history (our inference). Don't loop pushes or webhook calls quickly to force a run; it adds load to the same shared limit (our inference).

Verified scope

Cursor Automations with PR, Slack or webhook triggers, October 2026.

Becomes obsolete when

Cursor queues or retries PR-, Slack- and webhook-triggered runs when the platform limit is hit, like it does for scheduled runs.