I have an automation that uses web application. It functions as expected when running the automation using Pega Robot Studio 22.1. However, when I am running the automation using Pega Robot Runtime 22.1, the web application is not responding accordingly.
Scenario in Pega Robot Runtime 22.1: When the automation is started, it will open the web application, the automation is expected to log in, however, given that there is already a long pause, the automation was not able to see the object even the web application is already opened. This is not happening in Pega Robot Studio 22.1.
What is the possible reason for this? What is the possible solution to fix this?
Have you chosen the adapter as web adapter/universal web adapter.
On the start page have you mentioned the URL correctly in which your automation wants to open and also I suggest you to check the StartMethod field as false or true.
@KamineniSurya yeah, I have done all that you mentioned. It is so weird that I am not encountering the issue when I run the automation in Pega Robot Studio.
@LizetteL On your Runtime machine, please check that you have the Pega Browser Extension application installed. Check to see that your browser extension is enabled in Chrome (or Edge, whichever one you’re using). When you launch Chrome (or Edge), if the extension is enabled, you should see a new process launch in Task Manager named “Pega.Web.MessagingHost.exe” (switch to the Details tab in Task Manager to locate this process). If you see that process launching with your browser, you know the extension is installed an enabled. I suspect this is what your problem is.
@ThomasSasnett Robot Studio and Robot Runtime are on the same machine. I am just using the Robot Runtime (runtime included in the installer of Pega Robot Studio) to run the automation. I also have other web application in my automation, but it did not encounter the same issue.
I have attached the screenshot of my Chrome setting and Task Manager.
@LizetteL I would suggest that you open a support request to demonstrate this issue. Xray Vision should not exhibit this behavior and having the issue reported would allow us to get it corrected even if you do not require it.