Unable to Trigger Unattended Job via API - "Couldn't find any user with unattended robot permissions in the current folder" Error

[Leila]

Environment:

• Orchestrator: UiPath Cloud (cloud.uipath.com)
• Organization: relentlessautomate
• Tenant: DefaultTenant
• Folder ID: 7205013
• Process Name: Test-Trigger
• Release Key: 222f0746-6069-4740-90b2-d9286e601f57
• Process Key: Solution.Rpa.RPA.Workflow
• Robot: Default Robot (ID: 12764233, Type: Unattended)

---

Problem Description:

We are unable to trigger an unattended job via the UiPath Orchestrator API. When making a POST request to start a job, we consistently receive the error:

Your request is invalid or could not be processed by the service
Couldn't find any user with unattended robot permissions in the current folder.

---

What We’ve Tried:

1. Process Configuration:

• Created RPA workflow in UiPath Studio Web with 4 input arguments (in_supabaseUrl, in_filePath, in_supabaseKey, in_documentId)
• Successfully published workflow to Orchestrator (multiple versions)
• Created process in folder 7205013 from the published package
• Verified process shows all 4 input arguments correctly
• Confirmed process is using the latest published version

2. Robot Verification:

• Confirmed “Default Robot” exists (ID: 12764233)
• Robot Type: Unattended
• Robot Account Type: Robot account
• Verified robot is assigned to folder 7205013 (URL shows fid=7205013 when viewing robot permissions)
• Robot has “Automation User” role in folder 7205013
• Role shows as “Direct assignment, Inherited from group(s) automation users”

3. API Request Attempts:

We’ve tried multiple strategies to start the job:

Attempt A - JobsCount Strategy:

json

{
  "startInfo": {
    "ReleaseKey": "222f0746-6069-4740-90b2-d9286e601f57",
    "Strategy": "JobsCount",
    "JobsCount": 1,
    "InputArguments": "{\"in_documentId\":\"...\",\"in_filePath\":\"...\",\"in_supabaseUrl\":\"...\",\"in_supabaseKey\":\"...\"}"
  }
}

Result: “Couldn’t find any user with unattended robot permissions in the current folder”

Attempt B - All Strategy:

json

{
  "startInfo": {
    "ReleaseKey": "222f0746-6069-4740-90b2-d9286e601f57",
    "Strategy": "All",
    "InputArguments": "{...}"
  }
}

Result: Same error

Attempt C - Specific Robot Strategy (numeric ID):

json

{
  "startInfo": {
    "ReleaseKey": "222f0746-6069-4740-90b2-d9286e601f57",
    "Strategy": "Specific",
    "RobotIds": [12764233],
    "InputArguments": "{...}"
  }
}

Result: Same error

Attempt D - Specific Robot Strategy (string ID):

json

{
  "startInfo": {
    "ReleaseKey": "222f0746-6069-4740-90b2-d9286e601f57",
    "Strategy": "Specific",
    "RobotIds": ["12764233"],
    "InputArguments": "{...}"
  }
}

Result: Same error

4. API Endpoint & Authentication:

• Endpoint: https://cloud.uipath.com/relentlessautomate/DefaultTenant/orchestrator_/odata/Jobs/UiPath.Server.Configuration.OData.StartJobs
• Method: POST
• Headers:
  • Authorization: Bearer [VALID_TOKEN]
  • Content-Type: application/json
  • X-UIPATH-OrganizationUnitId: 7205013
• Authentication is successful (we do NOT get 401/403 errors)
• Folder ID header is correct (verified from Orchestrator URL)

5. Manual Testing:

• When the workflow is tested manually via “Debug on Cloud” in Studio Web, it executes successfully
• This confirms the workflow itself is valid and functional

---

What We’ve Observed:

1. The robot shows “Automation User” permissions in the Folder Access tab
2. When viewing robot permissions at /robots/configured/12764233/view-permissions?tid=2278722&fid=7205013, the folder displays as “Shared (Role: Automation User)”
3. No other folders are listed in the robot’s folder access dropdown
4. The error specifically mentions “unattended robot permissions” - we’re unclear if the “Automation User” role includes the necessary permissions to execute jobs via API

---

Questions:

1. Does the “Automation User” role include permissions to execute unattended jobs via API, or do we need a different role?
2. Are there additional folder-level or robot-level configurations required to enable API-triggered unattended execution?
3. Is there a way to verify/troubleshoot robot permissions specifically for API job execution?
4. Could there be an issue with how the robot account is configured in folder 7205013?

---

What We Need:

Step-by-step guidance on configuring the robot and folder permissions to enable unattended job execution via the Orchestrator API, or identification of what configuration is missing/incorrect in our current setup.

---

Additional Context:

We are building an automation workflow where n8n triggers UiPath via API to process documents. The entire integration is working except for this final permission issue preventing job execution. I have been working on this for 8 hours straight literally.

Thank you for your assistance.

[marian.platonov]

But the robot is an unattended robot or an attended robot?

Based on the error, there are no robots assigned to the current folders.

• Check the user folder assignments and confirm there are users directly assigned to the folders

• For the assigned users, check if the unattended robot is enabled under the Tenant → Manage Access → Access Rules → Robot accounts → Edit robot

  At the tenant level, make sure to have the Allow to be Automation User role and Automation User role at the folder level.

  

  The users need to be explicitly assigned to the folders. The robots will are not inherited from the groups

[Leila]

UiPath is only allowing me to assign access to the Shared folder..not the folder where my process is.

[Leila]

Thank you , I am trying to do so, but UiPath is not even letting me select the folder where my process is stored. When I search it in the search bar to give folder access to ANY robot, only the generic “Shared” folder is populating as a folder choice. (see above response)

I appreciate the help