Question
Ruleset Drops on Scheduled Automations
Having an issue where our scheduled automations aren't starting because the ruleset drops when the job starts. The workgroup will switch to the scheduled setting; however, the ruleset drops and the job fails. I've noticed the operator id has a new save point at that time, so it's updating the profile when this happens. Is this a known issue - what can I do to prevent it? Thanks
Accepted Solution
Hello @MichaelM4236,
I think the issue might be related to the configuration for the robot registration. The robot operator record is created automatically by the registration process using the operator record defined as registration in the configuration as profile. In your case, that operator looks like was updated manually by the administrator after the registration process.
The best course of action would be for you to open a support ticket and post the ID here for GCS and ourselves to engage directly with you on a session where we can check your configuration and observe the behaviour.
Thanks
@MichaelM4236I am not sure I am following what you are saying. Are you saying that the operator is being updated and no longer has the appropriate ruleset available to perform the work?
What version of Pega Platform are you running? What version of Pega Robot Manager? I assume this is unattended, but if I am incorrect, please correct me. Would you provide a little more detail about what you are seeing? If you can include screenshots of the operator(s), that would help.
@ThomasSasnett I'm using 19.1 for Pega Robot Studio and version 8.6.1 for Robot Manager. Can I email you the screenshots - it's not allowing me to upload them for some reason... gets to 99% but won't go all the way through.
When a scheduled action occurs, you'll see the "updated by" column switches from admin to agent. In the following screenshot, the ruleset at the top is empty where it normally says EstesRPA. Not sure why it drops when the scheduled job takes off
@MichaelM4236 You may email them. First Name dot last name at pega dot com. You might need to reach out to support however as this sounds like something that might need a hands-on look. If you do, please add the INC to this post so we can track it.
It may be that your registration operator is missing the proper access group or ruleset. That might be something to look into. You might delete your current bot operators and have them re-register. You also might look at your registration decision tables to see if you have anything going on there that you may have misconfigured.
@MichaelM4236 I can't say that I have ever seen a bot remove its ruleset before. The only thing I can suggest is to ensure that the registration operator is setup correctly. One other thing I have done before is to delete the current operator IDs and allow them to be recreated upon registration. If there is still something else coming after and updating them, that would need to be investigated by our support team. I have forwarded this post to our product manager for Robot Manager; however, he is out of the office until the new year. I will do some more checking tomorrow to see if I can recreate this.
Accepted Solution
Hello @MichaelM4236,
I think the issue might be related to the configuration for the robot registration. The robot operator record is created automatically by the registration process using the operator record defined as registration in the configuration as profile. In your case, that operator looks like was updated manually by the administrator after the registration process.
The best course of action would be for you to open a support ticket and post the ID here for GCS and ourselves to engage directly with you on a session where we can check your configuration and observe the behaviour.
Thanks
@Angel Hermira Thanks - I will forward to our team and see if it's something they can reconfigure first - then open a ticket if not. It's an intermittent issue which is the weird part. Will work fine for a week or two then all of sudden drop