Question
Rakuten Card Co., Ltd.
JP
Last activity: 9 Feb 2023 1:39 EST
Processing when a Queue accumulates in RobotManager for a long time
If the terminal for robot processing has crashed and RobotRuntime has not started, the queue cannot be processed.
If there is a delay in recovery, the queue will be stuck for a long time.
We are considering the following methods to deal with this situation.
Is it possible to configure the following settings using the basic functions of the product without coding?
If so, please provide us with a reference document or a configuration method.
(1) A setting that treats a queue as an error if it is not processed for a certain period of time on RobotManager.
For example, if a queue is not processed for 60 minutes after it arrives at RobotManager, the queue is forcibly treated as an error.
(2) Notify when a queue arrives while RobotRuntime is not running.
If a queue arrives in a situation where the robot cannot process it, it will be notified by e-mail or log.
Accepted Solution
Updated: 9 Feb 2023 1:39 EST
Pegasystems Inc.
GB
Hi @ShunsukeM6155,
Please, correct me if I'm wrong but I believe that when you refer to queue, you refer to the assignment in the queue, not to the queue itself as this last it is the container for the assignments that the robot runtime will process.
If I understood correctly your question, you want to be notified if the assignment is not being processed by the robot in a certain defined time.
You can achieve this by defining the SLA https://docs-previous.pega.com/case-management/87/setting-service-level-agreements-slas-stages-processes-and-steps in the robotic assignment https://docs-previous.pega.com/case-management/87/assigning-task-robotic-work-queue
In your example you could setup the notification in the Goal section of the SLA to 1minute after the assignment is created and the Deadline section to resolve the assignment as an error and send the pertinent notification too.
Please, let us know if you have further questions.
Angel