Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Varun Kattimani (VarunK03) National Australia Bank Ltd
National Australia Bank Ltd
AU
VarunK03 Member since 2020 19 posts
National Australia Bank Ltd
Posted: Jun 28, 2022
Last activity: Jun 29, 2022
Posted: 28 Jun 2022 21:16 EDT
Last activity: 29 Jun 2022 20:30 EDT
Closed

Browser gets closed/Crashed when bot is triggered from PEGA Case

Hi Team,

Greetings,

We are facing and issue were the browser gets closed (Chrome/Edge) when a RDA bot is triggered from Pega case.

Open a Pega Case and trigger RDA integrated bot, the bot performs the automated steps on the target application(Siebel.exe) (Configured as windows adapter) and as it completes the task it returns the response back to Pega Case, the pega case which is opened in browser, all the instance of the browser(either Edge or Chrome from where it gets triggered) gets closed/crashed automatically.

Runtime version : 19.1.66 : The bot functionality was working fine like an year, and the issue was observed recently on one user. 

Now we upgraded to 19.1.108 for edge support, the issue is occurring even in the latest runtime version as well when triggered from Edge browser. We are not able to replicate in dev environment, its observed only on prod user machine.

Note : Chrome browser has been decommissioned at organization level. Pega robot extension for edge browser is disabled as the specific RDA bot does not work with any web application.

 

Have we noticed these kind of issues earlier ? any pointers on how we can troubleshoot the issue ?

PNF : Proprietary information hidden2

Win OS : 21H2

Thanks and Regards,

Varun

To see attachments, please log in.
Pega Robotic Desktop Automation Robotic Process Automation Financial Services Robotics System Architect

Posted: 2 years ago
Posted: 29 Jun 2022 17:55 EDT
Thomas Sasnett (ThomasSasnett) MOD Lead Robotics Architect
Pegasystems Inc.
US

@VarunK03 This issue will likely need some logging to assist you with. I suggest opening a support request and they can setup a meeting to collect the required logs to determine the issue. It doesn't seem likely that the communication back to the Pega case is actually the cause of Edge crashing. As that same communication would be sent to trigger the automation as well. If you don't have any interaction with Edge other than via the Robot Activity, then this may well be a problem on your Pega Platform application. In either case, it is an issue that support should have a look at.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice