Pega Automation Scheduling Service doesn't work as expected
Hi Team,
We have built a RPA BOT and need to deploy to an unattended server. BOT should run on daily basis at a specific time in the day. Server on which BOT needs to be deployed will be unattended (locked).
We've explored different options including Windows Task Scheduler, Windows Service and Pega Scheduler.
BOT has functionality to interact with different applications (Ex: Launch excel and perform tasks). A batch file is created to launch and Runtime and trigger BOT execution.
Hi Team,
We have built a RPA BOT and need to deploy to an unattended server. BOT should run on daily basis at a specific time in the day. Server on which BOT needs to be deployed will be unattended (locked).
We've explored different options including Windows Task Scheduler, Windows Service and Pega Scheduler.
BOT has functionality to interact with different applications (Ex: Launch excel and perform tasks). A batch file is created to launch and Runtime and trigger BOT execution.
- Issue with Task scheduler is that batch file runs and BOT works as expected when "Run only when user is logged in" option is selected. But fails to launch runtime when "Run whether user is logged on or not" option is selected (Pls refer snapshot1.png).
- Issue with Widows service is that batch file is launched, openspan.runtime.exe can be seen in task manager, but fails to run BOT
- We've also explored Robotic Processing Automation Scheduling service. Followed the steps as described in "https://community.pega.com/knowledgebase/articles/robotic-processing-automation-scheduling-service". But BOT doesn't run.
- Installed OpenSpan.WinLogon.Service.exe, updated registry values
- Copied RuntimeConfig.xml and RPASchedule.json to "C:\Program Files(86)\Openspan" path.
- Updated startupProject value in RuntimeConfig.xml (snapshot2.png)
- Updated RPASchedule.json to launch BOT once in a day at a specific time
- Restarted OpenSpan services in services.msc
Kindly suggest a solution to run BOT (should interact with desktop) on unattended server.
Here are the environment details:
Pega : 8.0.1093
OS: Windows 7 64 bit
Accepted Solution
Pegasystems Inc.
US
The resolution to the SR was the following:
- Installing the OpenSpan.WinLogon.Service.exe.
- Steps to Install the service:
- Log on as an administrator or open a command prompt window as admin.
- Navigate to the .NET Framework folder. You can use any version of Framework that is 4.0 or later.
- Below is a sample screenshot:
- Steps to Install the service:
The resolution to the SR was the following:
- Installing the OpenSpan.WinLogon.Service.exe.
- Steps to Install the service:
- Log on as an administrator or open a command prompt window as admin.
- Navigate to the .NET Framework folder. You can use any version of Framework that is 4.0 or later.
- Below is a sample screenshot:
- Steps to Install the service:
- Set the credentials for the credmgr to use.
- Link to the commands to set the credentials: https://community.pega.com/knowledgebase/articles/pega-robotic-automation-credentials-manager-utility
- NOTE: the Runtime user credentials are so that you can start Runtime under different user than the one that logged into the machine.
- Configure the CommonConfig as specified in step 4 in the following link: https://community.pega.com/knowledgebase/articles/configuring-robotic-automation-runtime-robotic-process-automation
Pegasystems Inc.
US
The Robotic Processing Automation Scheduling is definitely the way to go. I'd recommend opening a Support Request after turning on the Scheduler logs and checking where the failure is happening. You can enable the logs based on the information in the attached document. Make sure to attach the logging with the SR when you open it.
Infosys
IN
Hi Team,
Windows login credentials are configured in credmgr.exe.
Here is the latest update. Scheduler is able to trigger the automation/BOT in specified time. But the behavior is not as expected.
Here are our queries
- Duration time is set for 900 minutes (15 hrs), and automation takes 1 min to complete. Start time is @8AM. So scheduler should continuously restart runtime (trigger BOT) from 8AM till 11PM. But this is not happening
- BOT should trigger BOT twice in a day at 10AM & 7PM. This cannot be achieved using Pega scheduler and can only be done using Task scheduler. Send keys fail to work when BOT tries to run in locked state. Task scheduler won't unlock machine when it triggers the BOT
Pegasystems Inc.
US
Yes. Pega Scheduler can only schedule Runtime to Start and Stop once in a 24 hour period. The start time is when the Scheduler will attempt to unlock the machine and start the OpenSpan.Runtime.exe process. At the end of the duration period, the Scheduler will call OpenSpan.Runtime.exe to shutdown and the machine will be locked again.
Accepted Solution
Pegasystems Inc.
US
The resolution to the SR was the following:
- Installing the OpenSpan.WinLogon.Service.exe.
- Steps to Install the service:
- Log on as an administrator or open a command prompt window as admin.
- Navigate to the .NET Framework folder. You can use any version of Framework that is 4.0 or later.
- Below is a sample screenshot:
- Steps to Install the service:
The resolution to the SR was the following:
- Installing the OpenSpan.WinLogon.Service.exe.
- Steps to Install the service:
- Log on as an administrator or open a command prompt window as admin.
- Navigate to the .NET Framework folder. You can use any version of Framework that is 4.0 or later.
- Below is a sample screenshot:
- Steps to Install the service:
- Set the credentials for the credmgr to use.
- Link to the commands to set the credentials: https://community.pega.com/knowledgebase/articles/pega-robotic-automation-credentials-manager-utility
- NOTE: the Runtime user credentials are so that you can start Runtime under different user than the one that logged into the machine.
- Configure the CommonConfig as specified in step 4 in the following link: https://community.pega.com/knowledgebase/articles/configuring-robotic-automation-runtime-robotic-process-automation
Ford Motor Company
IN
In order to restrict the number of runs during the schedule and duration, you can try the following:
- Change RpaSchedule.json file to trigger the package @10 AM and set DurationTime between 550 to 600 mins
- Open OpenSpan.WinLogon.Service.exe.config file.
- Change RuntimeLaunchRetryCount Value to 1 to run it one more time. Change RuntimeLaunchRetryIntervalMins Value to 540. I hope this will trigger the next run after 540 mins which is 7 PM.
- Change RuntimeLaunchRetryCount Value to 0 to run it only once.