Pega Robot runtime getting Robot Assignment
Hello Dear Pega enthusiasts,
I have a question regarding getting assignment by robots from Robot queue in Robot manager. Robot usually does not the case from the queue immediatly , it waits 30seconds.
My question is how to manage polling interval for robot in RPA?
I know this has been answered in 2017 here: https://collaborate.pega.com/question/how-manage-robot-polling-interval-rpa
Hello Dear Pega enthusiasts,
I have a question regarding getting assignment by robots from Robot queue in Robot manager. Robot usually does not the case from the queue immediatly , it waits 30seconds.
My question is how to manage polling interval for robot in RPA?
I know this has been answered in 2017 here: https://collaborate.pega.com/question/how-manage-robot-polling-interval-rpa
but if there has been any changes I would appreciate. as our solution is running live.
Our current solution runs live, where client submits data on the webpage, these data go to backend system then to pega platform, then directly to robot in VM where robot processes the case in our system application, when finishes its job, robot returns result back to front end system, where client waits currently 1-2min.
our approach is to reduce this time as in 21st century client should not wait 2min in front of the screen, waiting results from his request.
BR
David
Accepted Solution
Updated: 5 Feb 2020 8:22 EST
Boubyan Bank
KW
Hello David,
from robot manager dashboard > settings > HeartBeat
, for the Pega Agents - as I said - this one has to be confirmed by Pega Team
alternative --- In Pega Platform ->>
-
Record.
-
Expand SysAdmin > Dynamic System Settings.
-
Click Pegarobotics/HeartbeatInterval in the Pega-ProcessEngine ruleset.
Hello David,
from robot manager dashboard > settings > HeartBeat
, for the Pega Agents - as I said - this one has to be confirmed by Pega Team
alternative --- In Pega Platform ->>
-
Record.
-
Expand SysAdmin > Dynamic System Settings.
-
Click Pegarobotics/HeartbeatInterval in the Pega-ProcessEngine ruleset.
-
In the Settings tab, in the Value field, enter the interval, in seconds, during which each VM sends a heartbeat to the system.
-
Click Save.
Boubyan Bank
KW
hello David,
there are two factors -
- this one has to be confirmed by Pega Team,
the agents related to Robotics , classs- roboticsAutomationCaseManagement ) are responsible for this delay, every 30 seconds / 45 seconds the agents ( running in Pega background ) pick the case
- the heartbeat
A Major factor, runtime communicates with Pega with this interval , it can be reduced
But , the generated rpa logs will make the performance slow- in such case , we used to disable the default log4Net logging of RPA service ( pls Note : no change in Runtime logging)
David Taliga
AT
Thank you very much for your answer Bhabanisha,
I thought pega robotics runtime which runs in the VM is responsible for picking up the cases, it pulls the case from the queue when it is ready to process some new case. Does it it work like this ?
Regarding your asnwer
- In PEGA Platform, please did you mean this setting in Pega Platform ? (below in the screenshot marked in yellow ,screen.PNG)
- can be the heartbeat changed in pega robot config files ? like runtimeconfig.xml or studioconfig.xml ? or only in Pega Platform ?
BR
David
Accepted Solution
Updated: 5 Feb 2020 8:22 EST
Boubyan Bank
KW
Hello David,
from robot manager dashboard > settings > HeartBeat
, for the Pega Agents - as I said - this one has to be confirmed by Pega Team
alternative --- In Pega Platform ->>
-
Record.
-
Expand SysAdmin > Dynamic System Settings.
-
Click Pegarobotics/HeartbeatInterval in the Pega-ProcessEngine ruleset.
Hello David,
from robot manager dashboard > settings > HeartBeat
, for the Pega Agents - as I said - this one has to be confirmed by Pega Team
alternative --- In Pega Platform ->>
-
Record.
-
Expand SysAdmin > Dynamic System Settings.
-
Click Pegarobotics/HeartbeatInterval in the Pega-ProcessEngine ruleset.
-
In the Settings tab, in the Value field, enter the interval, in seconds, during which each VM sends a heartbeat to the system.
-
Click Save.
Boubyan Bank
KW
the one which, you specified is the timer for all agents , I assume, which means , in 30 seconds all agents gets refreshed , but not sure on this ...
try with heart beat , and follow the 2nd step in my main answer