I encounter this issue everyday and a colleague of mine found a workaround. Hopefully, this points you in a direction towards a solution.
My script goes like this:
- Open a CSV file
- Read column data into variables
- Click Link Tab 1 on page
- Search something (col1)
- Click Link Tab 2 on page
- Update something (col2, col3, …)
- Done
I use the Play Loop to run through the rows of data (e.g., Start Value: 3, Max: 42)
We run the “play loop” for this script maybe 5-10 times every single day. I could have a loop of 50 and it goes without ever stopping. I could have a loop of 3 and it will stop at loop 2.
What we’ve noticed lately when it stops is that by simply clicking the tab again, Kantu wakes up and continues (Pause, Resume doesn’t seem to work anymore). So if I can see the script stopped in step 4, I’ll just click on Link Tab 1 and the script wakes up and continues. If the script stopped in step 6, I’ll just click on Link Tab 2 and it wakes up and resumes on its own.
Of course, what I’m really saying is we can’t trust it to run unattended, which defeats the entire purpose of automating. So it’s a big thorn on the beauty of UI.Vision. I’m actually expanding my code to include error handling. That will at least help me identify where it stopped.
It seems that it has to do with the load time of the page somehow. We have 3 sets of scripts. All of them, we run via Play Loop.
The two of them go through quite a bit of steps (1-7 above is oversimplified). There’s several “clickandwait” so it’s more often prone to randomly stopping in the middle.
The third one is very straightforward. One “clickandwait” to get to the page. Then on the same page, we click create, fill-in date, update. We loop 5 to 60 times to click, create, fill-in, update. It does still stop sometimes, but not anywhere near as often as a more complex cycle.
Let me know if you haven’t found any reproducable example. I could try to create a dummy website and write a similar script/csv/play loop to emulate what we’re doing in production. And hopefully be able to reproduce the issue and share it with your team.