Posted: 24 May 2019 7:39 EDT Last activity: 27 May 2019 5:18 EDT
excel connector not working as expected
Please help on this urgent question. We have a bot which reads data from a ticket/ item from a list, clicks on that item, opens a workbook and copies data into a workbook into 3 different tabs, based on values in the Excel the bot writes a decision into the workbook and then closes the workbook. moves onto the next item on the website and then processes it the same way by opening a workbook. Now I have noticed a strange pattern. On every fifth iteration, the bot stops when its writing data into the first tab of this fifth excel, It does not give any error, just stops. I am not sure how to debug this.. On thing related to this is, I see many excel processes running, it seems like for each iteration the bot starts 2 excel processes and this issue could be due to system not being able to handle all these excel processes.
***Edited by Moderator: Lochan to update platform capability tags***
The automation stops means that the IE browser hangs/stuck at this stage? Have you implemented any async link where a button click is navigating to a new page? If not implement the async link where a button click is navigating to a new page OR at each iteration of the for loop. Check memory utilization at the stage where IE hangs.
If issue still replicates after implementing the async link, revert the changes. Also let me know the version of Robotics used.
Thank you for your revert. IE does not hang. The bot just exists and stops execution. It always happens on the fifth execution. It stops in between when the bot is writing data into first tab of the excel(n particular cell, it varies but always tab 1). No particular pattern other than it stopping on fifth item. version is 8.0.1084
Posted: 2 years ago
Posted: 27 May 2019 5:18 EDT
Srinivasa Rao Bitra (raos)
Manager - Global Client Support
If async link not implemented, you can try as suggested in earlier thread and try to reproduce the issue. Replicate the issue and upload verbose runtime.log file. If you are using the same data for testing, you can check if any data causing this issue because the issue is always replicable at 5th iteration.