Failed to get default branch: User and team ID are not set

[Andrew_Grange]

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

When trying to do a test run of an automation I get the error seen in the screenshot.

Steps to Reproduce

Create an automation with the following JSON structure.

{
“name”: “",
“triggers”: [
{
“cron”: {
“cron”: "20 4 * * "
}
}
],
“actions”: [
{
“mcp”: {
“server”: {
“id”: “1096119”,
“name”: “playwright-mcp”
}
}
}
],
“prompts”: [
{
“prompt”: ""
}
],
“agentOptions”: {
“privateWorker”: {
“labels”: [
{
“key”: “name”,
“value”: ""
},
{
“key”: “cursor.private_worker.shared_assignment_allowed”,
“value”: “true”
}
]
}
},
“memoryEnabled”: true,
“scope”: “private”,
“gitConfig”: {
“repo”: "https://gitlab.com/",
“repos”: [
"https://gitlab.com/**”
],
“branch”: “”
}
}

Expected Behavior

I’d expect to be able to do a test run and if a default branch is needed I should have an option to specify it.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Web Client with agent cli at version: 2026.05.09-0afadcc

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the detailed report. The JSON and screenshot really helped. This is a bug on our side. For individual Pro accounts without a team, the automation context does not fetch the user or team ID, and resolving the default branch fails with this error. I’ve reported it internally.

While we’re fixing it, here’s a working workaround. Set the branch explicitly in gitConfig instead of an empty string, so auto-resolve won’t run:

"gitConfig": {
  "repo": "https://gitlab.com/***",
  "repos": ["https://gitlab.com/***"],
  "branch": "main"
}

Replace main with the branch you need. After that, Run Test should pass.

I can’t share an ETA for the fix yet, but I’ll reply in the thread once there’s an update.

[deanrie]

Hey @Andrew_Grange, quick update: we fixed the bug where automations using a GitLab repo with an empty branch field couldn’t resolve the default branch on individual Pro accounts. The workaround of setting the branch explicitly is no longer needed.

Can you run a test run of your automation again with the branch field left empty and let me know if it works? If the error still shows up, please share the latest details and we’ll take a deeper look.