Question
Nationwide Building Society
GB
Last activity: 4 Feb 2026 10:49 EST
Creating runtime package with RPA Service query
As we are looking to introduce unattended robots into our overall robot estate we need to update our runtime package to include the RPA component
Our challenge is to create one package which includes the RPA component that would be deployed to all bot devices, attended and unattended, but with an additional commonconfig file dependency which has all the RPA settings: Robot manager URL etc, just for the unattended devices
We are creating something similar with our 22.1.53 runtime package whereby we have a base runtime installation but with an additional commonconfig file for those devices requiring access to a Pega application & Constellation service
Based on my investigation so far I am not certain that the RPA packaging challenge is possible as stated above - this is because
After package installation the RPA service is by default disabled
The only way to enable it is via a group policy update which would impact all devices (as per Pega documentation)
For attended robots where there are no user profiles created in the pega platform the user would run into authentication issues when the RPA service is started and attempts to access the Robot manager
This is my understanding so far and it may be incorrect which is why I am creating this post for advice
It may be the case that we do require a second package specifically configured for RPA which would deployed only be to unattended devices
Pegasystems Inc.
US
When the RPA Service is installed, it is not disabled—its startup type is set to Manual. When you install the runtime, it also installs the Pega Synchronization Engine, which includes the Pega Updater Service. The Pega Updater Service is configured to start automatically.
When the Pega Updater Service starts, it checks each installed product for required updates. After each product completes its initialization, the service executes the product’s configured Post‑Initialization action. For both the RPA Service and PNF, that Post‑Initialization action starts the service.
The RPA Service will stop if the CommonConfig has an invalid Robot Manager Url or is not enabled.