Manage Schedules with Unattended Bot

Help Robot
,
1

I created a workflow that disables schedules/triggers and stops jobs for selected processes. This works great from my development machine. However, when I promote it to run from a Time trigger on an Unattended bot I get the following error:

Disable Trigger status code: 403
Response: {“message”:“You are not authorized!”,“errorCode”:0,“result”:null,“targetUrl”:null,“success”:false,“error”:{“code”:0,“message”:“You are not authorized!”,“details”:“You are not allowed to perform this operation.”,“validationErrors”:null},“unAuthorizedRequest”:true,“__abp”:true}

I have the bot Tenant permissions set as follows (I am sure I went overboard with permissions out of frustration):

The image shows the "Manage Access" section of the "Tenant" in an application interface, listing access rules for two accounts, srvcebotprod17 and uiprdrbot017, both assigned roles with various administrator permissions. (Captioned by AI)
The image shows the "Manage Access" section of the "Tenant" in an application interface, listing access rules for two accounts, srvcebotprod17 and uiprdrbot017, both assigned roles with various administrator permissions. (Captioned by AI)1453×317 45.6 KB

I have the folder permissions set as follows (again, I am sure they are more than needed):

The image shows a screenshot of a directory in a folder management system with accounts, groups, and permissions for a "BotManagement" folder. (Captioned by AI)
The image shows a screenshot of a directory in a folder management system with accounts, groups, and permissions for a "BotManagement" folder. (Captioned by AI)1625×325 45.6 KB

BotManageFolderAddOn Includes View and Edite permissions for Jobs, Processes and Triggers. This should also be included in Folder Administrator which I only added recentle out of frustration.

srvcbotprod17 is the service account
uiprdbot017 is the robot account with machine template environment.

I am using Orchestrator HTTP activities for all requests - again, these are working perfectly for me - I am Orchestrator Admin and Folder Admin.

Orchestrator Cloud with on-premise machines UiPath v.2024.10.1

2

Hi @gregg.rubright,

What is it you are doing different from bot account this time?

I see disable/enable triggers from bot account has worked for you in the recent past. Do you recall anything that has changed recently which could be interfering with the working?

Regards
Sonali

3

Well that is the thing. This was working great up until about 3 weeks ago. But I didn’t change the trigger or bot permissions at all.

4

Hi @gregg.rubright,

Was there any UiPath version upgrade done?

Are you still on the same versions as you were before?

Regards
Sonali

5

We are still on the same version since mid Summer.

6

Hi @gregg.rubright,

Are you able to please verify the points stated in below post? By any chance, has your machine changed?

Regards
Sonali

1 Like
7

I am not great at server side issues but I will try to answer as best I can. The bot account has not changed. We do operate in a Citrix environment with several machines in a template configuration so I am not 100% sure about which machine it is coming from. Orchestrator (the recipient of the call) is in the cloud.
I have permissions on the account in my bot management folder to do the work as required from the swagger file. However, do I need to put that account in each of the folders where I am controlling the jobs and triggers?

8

Hi @gregg.rubright,

yes, whatever folders you need to run the jobs/triggers, you should be part of that folder.

you can’t do anything in a folder if you don’t have required rights in that folder.

having tenant level permissions is different from folder level permissions, we need both to be able to operate at folder level.

Regards
Sonali

9

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.