Question
Ford Motor Company Ltd
IN
Last activity: 5 Feb 2024 10:04 EST
STOP failed for Robot (HostName). The command message was not delivered to the robot.
- Enabled Auto-Balancing(AB) for two WGs and only single bot is available. Evalutation time is 60 mins.
- Please refer attachements for audit.
- It worked fine under first work group(operations) which is having an assignment of SLA of 3hrs. Once the 5hrs SLA of an assignment in another WG(TestV22) falls under the evaluation time, AB tried to stop the bot.
- Later observed a exception in audit from RM. Please let me know all the possible scenarios where RM might throw this particular exception. What changes we need to do in order to resolve it? Why the stop command is not getting delivered to bot?
- And when I tried to stop the bot manually it does not shows the optional at all. Only Terminate is available. In this way manual intervention is needed to terminate and run it. Please let me know why this happens and how to avoid it?
- Please let me know if you need any other details.
- Thanks.
Pegasystems Inc.
GB
Hi @Rakshith Mende,
The stop command seems to have failed to be delivered to the robot. This usually happens when there is an issue with the RPA Service.
When the stop command is unsuccessful, Robot Manager understands this and the only option available it is to terminate the robot. This is why you are only seeing that option in the menu.
The configuration that you describe should work fine. Which versions are you using for Robot Manager and the robots?
Thanks
Ford Motor Company Ltd
IN
Hello @Angel Hermira Thanks for the response. Yes understood it. But why RPA service is not working properly? Once bot is in StandBy mode and connected it was supposed to working at all the time right? There are no issues with network connectivity cause this a VDI. Why we are observed this irregular behaviour? Here are the requested details: Platform version 8.8.2 Runtime version Depends upon on package we use. For example 118 or higher. RPA service is 3.1.29 or higher.
Pegasystems Inc.
GB
Hi @Rakshith Mende ,
I cannot comment on the specific reason. I'd need to debug with you to understand why the command is failing to be delivered. If you don't mind, you can create an INC and ask GCS to have a session and involve me on that.
Happy to go through your configuration and debug together. Then we can update the finding back here for everybody's benefit.
Thanks