Question

Royal Bank of Canada
CA
Last activity: 29 May 2025 13:19 EDT
Pega Runtime Project Location
I'm upgrading one of our automations from v19.1.102 to v22.1 and I've noticed a difference in the way the runtime is loading the solution that's breaking our deployment process.
We deploy the project solution .pega file manually to a production NAS alongside other config files that are referenced by the automation. I have a module in the automation that gets the location for the currently running project and then uses that to locate the config file since the build and config are deployed to the same location. This worked well in v19.
However, I'm noticing now that v22 copies the project solution .pega file from the NAS to the local "AppData\Local\Pegasystems\22.1\Projects" folder on run-time. The issue now is that, since it doesn't copy any of our other files deployed to the NAS along with it, the automation can't locate them in AppData and it fails.
This all happens when I try running our batch script to run the project:
"C:\Program Files (x86)\Pegasystems\Pega Robot Runtime v22\Pega.RobotRuntime.exe" --package "NAS_LOCATION\Solution.pega"
This also happens if I add the NAS project location to the RuntimeConfig.xml as the startup project.
What's even more interesting is that, if I manually start the Runtime and manually load the project from the same NAS using the system tray, the pega runtime doesn't copy the solution .pega file to local AppData and actually runs entirely from the NAS. In this case, there are no issues and the automation runs as expected.
I'm upgrading one of our automations from v19.1.102 to v22.1 and I've noticed a difference in the way the runtime is loading the solution that's breaking our deployment process.
We deploy the project solution .pega file manually to a production NAS alongside other config files that are referenced by the automation. I have a module in the automation that gets the location for the currently running project and then uses that to locate the config file since the build and config are deployed to the same location. This worked well in v19.
However, I'm noticing now that v22 copies the project solution .pega file from the NAS to the local "AppData\Local\Pegasystems\22.1\Projects" folder on run-time. The issue now is that, since it doesn't copy any of our other files deployed to the NAS along with it, the automation can't locate them in AppData and it fails.
This all happens when I try running our batch script to run the project:
"C:\Program Files (x86)\Pegasystems\Pega Robot Runtime v22\Pega.RobotRuntime.exe" --package "NAS_LOCATION\Solution.pega"
This also happens if I add the NAS project location to the RuntimeConfig.xml as the startup project.
What's even more interesting is that, if I manually start the Runtime and manually load the project from the same NAS using the system tray, the pega runtime doesn't copy the solution .pega file to local AppData and actually runs entirely from the NAS. In this case, there are no issues and the automation runs as expected.
Is there a way, using a similar batch script as shown above, to force Runtime to always run the project from the NAS instead of copying it locally? We don't use Robot Manager and we need to have the automation scheduled to run once a week using Windows Scheduler.