Configuring the Bot Id in a New Runtime

HenryAnderson — Mon, 23 Feb 2026 15:40:29 GMT

Hello, I'm setting up a new Runtime from scratch, in v6.10.4. We use CyberArk to retrieve the password when the Bot run.

Installed and configured everything. But, when launching the process from 'Schedules' ('Run Now'), the Login Agent process is failing to retrieve the password from CyberArk. Here are some details:

- Login Agent process builds a URL and calls CyberArk which returns the password.
- The URL sent to CyberArk has the Bot Id; it is matched in CyberArk.
- The log from a successful login from an existing Runtime for an existing Bot is:
"........... ... [Object=Operating System-BluePrismRPA-xxxxxx-BOT00xx] ...........

- The log from the failed login attempt from the new Runtime for an existing Bot is:
"...........[Object=Operating System-BluePrismRPA-xxxxxx-] ........."

Notice the difference in the highlighted 'Object' values: the successful URL has Bot Id ('BOT00xx') and the failed one has nothing after 'xxxxxx-'. It is incomplete.

Essentially, the Bot ID is retrieved and added to the URL sent to CyberArk, which then matches with stored value. So, the new Runtime is missing a configuration/setup step to set the Bot ID. In our setup, a Runtime is tied to a specific Bot.

So, when a new Runtime is set up, somewhere in the configuration we need to define which Bot ID is to be used. I checked all configurations within Blue Prism; didn't find anything.

Thanks; appreciate the help.

topic Configuring the Bot Id in a New Runtime in Product Forum

Configuring the Bot Id in a New Runtime