Posted: 23 Jan 2017 5:09 EST Last activity: 6 Nov 2018 20:02 EST
How to manage robot polling interval in RPA
Does anybody knows how to manage polling interval for robot in RPA?
We are using RPA to integrate application on Pega 7.2.2 with a legacy system that doesn't provide rich enough API to communicate with. The scenario works quite fine except for one small problem: we are not able to configure how often robots are checking task queue.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Not sure that I understood you correctly, could you please provide more details? If robots act in respond to RobotActivity raised by Pega Robotics Console, then how can I configure Pega Robotics Console to raise RobotActivity more frequently?
I am working on a complete answer to your question and hope to have it later today. There are 2 pieces to the answer to your question - how does the Pega Robotics Runtime interact with the Robotics Console and how does your RPA solution interact with the Robotics Console.
The best way to explain this is to separate the answer into two parts, what the Pega Robotics Runtime does and what the RPA solution does.
The Pega Robotics Runtime is responsible for communicating with Pega 7. After the Runtime starts it registers with Pega 7 and requests work. If there are no assignments available it waits 30 seconds and then initiates another request. When it receives an assignment it raises a Robotic Activity Started event and waits until that activity completes. Once the activity is completed the cycle starts again with the Runtime requesting more work immediately. If there is no work available the 30 second wait occurs. The only time the Runtime will wait is if the WorkBasket is empty.
The RPA solution is event driven. It takes action only when a Robotic Activity Started event is raised. When all threads spawned by that event are released the Robotic Activity Completed event is raised. At this point the solution waits for the next Robotic Activity.
Currently the 30 second wait between requests for work by the Runtime is not configurable. If this is a value you would like to be able to control, you should make a request for this functionality.