Skip to main content

So we have an account made, to handle running bots with the API. We create saBotExecute, occasionally when we try to run bots with it using REST commands. The idea is you authenticate as saBotExecute, and put in the information to run a bot with REST commands that will also say which botrunner should be running. Issue is they will fail during the pre-processing phase. This is the error we were provided in the Audit log.

In 0-0 CS_ReleaseRoll SelectionStart: We found an issue that prevents the bot from running.

Access is denied

How can I check why this failed or how can I stop it from giving me an access denied?

 

The times the bot was launched appears to be identical. Are you trying to start the bot twice in rapid succession? That could definitely cause a problem.

You might get some more information from the three-dot menu on the right and see if there is more of a description in the information screen.

The times the bot was launched appears to be identical. Are you trying to start the bot twice in rapid succession? That could definitely cause a problem.

You might get some more information from the three-dot menu on the right and see if there is more of a description in the information screen.

It shouldn’t be. I click to have it create the request once and I can only send 1 payload. I did find this information on the subject. 

This could be due to missing permissions or features required to run a bot. Please ensure the following permissions are given to the runner user:

1. Run my bots
2. Schedule my bots to run
3. View content
4. Rename folder
5. Create folder
6. Credential Vault Permission
7. View Package
8. The Folder level permission
9. Permission on Subtasks
10. Global Variables

Hi ​@mercerj ,

 

Check if the User who is scheduling/deploying the Bots has View Package permission or not. 

If not, please provide the permission and try once.

 

Hope this will help. 

Reply


Terms & ConditionsCookie settings