BugBot fails after 20 minutes

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

BugBot

Describe the Bug

The bugbot runs for 20 minutes then fails with below error

Something went wrong. Try again by commenting “Cursor review” or “bugbot run”, or contact support (requestId: serverGenReqId_45c6d6a4-6dcc-4df4-a40f-7a52c7888dfc).

Steps to Reproduce

Push a PR, then manually run using bugbot run

Expected Behavior

Bugbot runs successfully and shows bugs/comments if any

Operating System

Windows 10/11

Version Information

Version: 3.3.30 (system setup)
VSCode Version: 1.105.1
Commit: 3dc559280adc5f931ade8e25c7b85393842acf30
Date: 2026-05-09T18:28:42.332Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the report and the request ID. This looks like a known class of BugBot timeout failures. About 20 minutes until a generic error usually means either an unhandled exception or an infra timeout somewhere along the way.

First, try retriggering it by adding a comment with @cursor review or bugbot run on the same PR. In similar cases, a retrigger worked because some of the data was already cached.

If it fails consistently on this PR, or on all PRs in the repo, a few details would help:

  • Is this a monorepo or a large codebase? Rough size in LOC and number of files
  • Is the PR diff large or small? Many files or lines vs just a few
  • Does it fail only on this PR or on all PRs in the repo?
  • Any new request IDs from fresh attempts

That’ll help us figure out if it’s hitting context size limits or something else. I can’t share an ETA for timeout fixes yet, but we’re tracking cases like this.

6

Repo has about ~123k lines, this is the first time im running cursor bugbot for the repo, and this fails for all the PR’s(Some PRs are very small - less than 100 lines of changes)

failure for the latest attempt

Bugbot couldn’t run

Something went wrong. Try again by commenting “Cursor review” or “bugbot run”, or contact support (requestId: serverGenReqId_8ccb0883-2a67-4340-ab2f-d9a71b94ac77).

7

Thanks for the info. 123k LOC on its own shouldn’t be a problem, and the fact that it fails even on PRs under 100 lines clearly doesn’t look like a context size issue. It sounds like something on the infra side or an initial repo setup issue.

I’ll take the second Request ID for investigation. To narrow it down faster, a few quick questions:

  • Is the repo private or public?
  • Is BugBot installed via the GitHub App on github.com, or is this GitHub Enterprise self-hosted?
  • Does the repo have any custom BugBot rules like .cursor/bugbot.md, .cursorrules, or similar?
  • Is the PR from a fork, or just a normal branch in the same repo?
  • In Cursor Dashboard, do you have any custom BugBot settings for this repo like model, rules, ignore paths?

In parallel, you can try removing and reinstalling the GitHub App for this repo in Cursor Dashboard: Settings → Integrations → GitHub. Sometimes permissions or the installation token get stuck during initial setup. After reinstalling, try bugbot run again.

8

Hi,

  • Its a private Repo
  • BugBot installed via GitHub App on github.com
  • No rules in the repo for BugBot
  • Its a normal branch not by fork
  • No custom settings in the cursor dashboard for the bugbot

Meanwhile, I tried unistall and re-install in the GitHub under Setting → GitHub App → Installed GitHub Apps but no luck

latest example below

Bugbot couldn’t run

Something went wrong. Try again by commenting “Cursor review” or “bugbot run”, or contact support (requestId: serverGenReqId_09286324-4faa-4e56-8348-c285463a0625).

Thanks,

12

Hey @Antony_Vilson,
I dug into the request IDs you shared and identified the issue on our end.

Your BugBot runs were being incorrectly blocked by a stale internal configuration related to a previous trial state. Your Pro plan includes BugBot, and you had plenty of usage remaining. The generic “Something went wrong” error was unfortunately masking the actual cause.

I’ve fixed the configuration on our end. Could you try running bugbot run on one of your PRs again and let me know if it works now?

13

Hi,

Unfortunately failed again, below is the request id for reference.

Something went wrong. Try again by commenting “Cursor review” or “bugbot run”, or contact support (requestId: serverGenReqId_fb456b8b-f57a-4a89-9c2c-80a85f0813d7).

Thanks

15

Antony, apologies — the earlier fix didn’t resolve this. I’ve escalated this to our engineering team with the full diagnostic data from your request IDs.

I’ll follow up here once the team has a fix or update. Sorry for the back and forth on this one.

16

Kindly provide an update.

Also, I have a question — if I upgrade my current plan, will this issue get resolved automatically? I need Bugbot urgently for a few tasks.

17

I think I’ve identified the specific step that’s failing.

Workaround you can try right now:

  1. Go to your Cursor Dashboard

  2. Under Preferences, find PR Summaries and set it to Off

  3. Try bugbot run on your PR again

This skips the failing step entirely. You’ll lose the PR summary comment, but the actual bug-finding review (which uses a different model) should proceed normally.

To answer your other question: no, upgrading your plan would not fix this. The issue is a server-side model failure, not a plan or usage limit.

Let me know if disabling PR Summaries unblocks you. Our engineering team is also investigating the underlying model issue.

18

Unfortunately, the workaround did not help. below is the reference id.

Something went wrong. Try again by commenting “Cursor review” or “bugbot run”, or contact support (requestId: serverGenReqId_1d45edc7-c7ed-4596-8c5c-3d3446901883).