Self Hosted Automations

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I am trying to use Automations with Self Hosted Cloud Agents, and I cannot specify the branch when connecting to Gitlab self hosted repos. When I try without a branch, the github actions was giving the following error:

Run HTTP_STATUS=$(curl -s -o /tmp/response.txt -w “%{http_code}”
HTTP Status: 400
{“success”:false,“error”:“Automation f2afca15-5573-426d-9d28-e0838ea28688 does not have a branch configured and could not resolve the default branch.”}::error::Cursor webhook returned HTTP 400
Error: Process completed with exit code 1.

When I added the branch as a query parameter inside the automation webhook url, it stopped giving this error but began giving a internal error, and it appeared on cursor failed runs with:

Webhook event
Automation failed
The automation run failed due to an unexpected error. Retry the run and contact support if the problem persists.

Also, there is another bug, I can’t turn on the option “Require Self-Hosted Pool for All Cloud Agents”. It turns on and immediatly goes to off.

Steps to Reproduce

I am trying to use self-hosted agents with Automations via github webhooks

Expected Behavior

It should work or give a more readable error message.

Operating System

Windows 10/11

Version Information

Web/Cloud Agents (Self-hosted)

Does this stop you from using Cursor

Yes - Cursor is unusable

6

@Colin Any updates on this one??

8

Hi Daniel!

Thanks for the detailed report. Both issues are confirmed on our end:

Branch configuration for self-hosted GitLab repos — The automation can’t resolve the default branch for self-hosted GitLab repositories, and adding the branch as a URL query parameter doesn’t work as a workaround. Our team is aware and working on improving GitLab support in automations.

“Require Self-Hosted Pool” toggle — This is a known bug where the toggle reverts immediately after being enabled. A fix is in progress.

No workaround for either issue at the moment, unfortunately. I’ll update this thread when the fixes land.

10

Is there an approximate ETA for when this will be fixed? We can’t use Cursor Automations in our company and rely on this functionality working.

11

Don’t have a timeline yet, but will update you when the fix is out, will try to push on the fix’s priority internally.

13

Any updates? @mohitjain