[Cloud Agent] Recurring Build are failing while manual ones work

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Hey,

In this environment: https://cursor.com/dashboard/cloud-agents/environments/e/e55acc86-e606-4706-b1e0-0d2c9b7d481b

Whenever I trigger a new build by hand, it works.

But when the recurring build (every hour I guess ?), I’m getting this error (but I don’t have any log).

Example build id : bld-20260904-e02c0904-8dd5-4184-9479-35f08c4b67ce

image
image1896×1046 62.2 KB

Could you help me understand why ?

Thanks in advance!

All the best,

Quentin

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

7

Hey @QChuret, thanks for the report and the build ID, that made this quick to track down.

Scheduled builds run under your team’s GitHub connection, while a build you start by hand runs with your own GitHub login. Right now the Cursor GitHub App installation on your GitHub organization is tied to an individual account that isn’t a member of your team in Cursor, so the team connection can’t use it. That’s why every scheduled build fails immediately (before a build machine starts, which is also why there are no logs) while your manual ones work.

To fix it:

  1. In GitHub, open the organization settings and uninstall the Cursor app from the organization.
  2. Back in Cursor, as team admin, open cursor.com/dashboard, go to Integrations > GitHub, and click Connect. Install the Cursor app in your GitHub organization again and grant it access to the repositories you use.
  3. Wait for the next scheduled build (they run about hourly) and check that it succeeds. A manual build won’t confirm the change because it uses your personal login.

If you know who originally installed the Cursor app, an alternative is to add that person to your team in Cursor; the next scheduled build will automatically adopt the existing installation for the team!