Bot is logging to the application and it’s processing the first item and completes successfully. It picks next item and while trying to enter the details in the application it’s not entering (waiting for sometime and gets exceptions and closes all applications). Then again logging into the application using credentials (from first step) and processing next item successfully. Again while processing next item it getting above mentioned exception. And so it is processing the first item after logging to the application and getting failed while processing next item.
Can anyone assist and provide insight as how to fix this issue?
I hope you are using the RE Framework. If I am not mistaken:
After entering the first queue item details, the application transitions to a state where no fields are visible for entering the details of the second queue item. When processing the second queue item, a system exception occurs, causing the bot to go through the initialization process and log in again. Consequently, the fields become visible, and the bot successfully enters the details for the third queue item into the portal.
To resolve this, please modify the code in the Process.xaml as follows:
→ After successfully entering all the details into the application, navigate back to the initial state (e.g., the home page). This way, the bot can easily execute the second queue item from a consistent starting point.
Hi @mkankatala
Thanks for the info. But already we are following the steps which you mentioned. Like, once first transaction completed, then bot goes to homepage of the application and enter the details of second transaction.
It was running good for last 30 days. But only from today iam facing this issue.
After submitting or getting back to Home Page check any popup window is opening… @Kumar_1308
In my recent process I faced the same issue, a Popup window is displaying when submitting after every transaction.
Try to debug the code and check after one transaction at which activity it was failing. If it was executing in Prod VM try to find out by checking logs.