@admin, I have the same issue, just uploaded the video of the issue
Note: It behaves the same, whatever website link it is
@admin, I have the same issue, just uploaded the video of the issue
Note: It behaves the same, whatever website link it is
1 Like
it happens randomly. But easier than that would be that someone please explains exactly how you manage to connect the script to the specific tab that you need. I have not been able to find it anywhere. Thanks
2 Likes
Also same problem… Could not believe that can demage whole automation… I’m opening 30 tab manually. After that,starting macro and finding text, store to csv and fuction tab=close, it supposed to continue work on another tab. It shows error #101. So after hard work, excel vba made for this macro, I need to start all again on another program. Perfect.
This has been a long existing problem. I observe it occurring at random on tabs where I have already run macro’s successfully. The error occurs before any macro code is executed, so it does not matter what is in the macro. Select Window will not fix the problem because again, it occurs before any macro code is executed. If I simple call the macro again, that is often sufficient to get the macro to run. I would say this error occurs almost 25% of the time I call macros. I don’t think the error is related to some of the explanations above. The error must be in the UIVision code and not in user macros.
@NWM It this about the #101 error? Please see my reply Error #101 Solution - #5 by admin for details.
If you think you found a bug, can you provide a video or at least screenshot of the situation?
i got this error 101 several times… on chrome latest version 101.0.4951.64 (Official Build) (64-bit) & windows 10
the solution is close the browser and reopen it… (this is on real desktop)
update: i cant run ui vision on chrome at virtualbox windows 10 OS. always got #101 error UI.Vision RPA is not connected to a browser tab
tried close and open browser several times… still got 101 error.
I’m still getting the 101 error after the 7.0.13 upgrade, unfortunately. But now also on tabs that previously were okay (tab=0). Here are my work arounds so far that seem to work…
- turn off all windows and app notifications e.g. reminders to update. These interrupt the focus and can cause a #101
- refresh every page before using (previously I was scrapping the dynamic page as it updated regularly)
- place a pause after every refresh and waitforpagetoload.
- place a 500ms pause after every tab change
- before running script refresh every page and click 3 tabs to ensure ui.vision is latching onto the correct window and tabs
- don’t do any real user actions on any browser windows while the script is running. Even if there are no Xclick commands.
Not all of the above may be needed with UI.vision 7.0.13.
The real winner command has been adding the bring browser to the foreground command to every cycle. My code has now passed the 48 hour mark. I’m happy, happy, happy after weeks of trying workarounds including different computers, browsers and OS.
The ui.vision extension is starting to have a big memory footprint (2.8Gb) and combined processes are sitting at 92% of memory. So it probably will fall over soon. But I’m happy.
- bringBrowsertoForegound
2 Likes
This is very interesting. Maybe Chrome slows done if not in foreground? We will keep this info in mind!
I realise this could be a ‘false positive’ on the bring browser to Foreground command. I went through my code and compared line by line with the previous version and found a Pause 2000 after I transferred to a tab with Whatsapp. This could also be the cause of my good fortune.
1 Like
Yes, this could be it!
After my code ran for 48 hours I had 4 days where I couldn’t get it to run for more than 10-20 minutes. And that is the same code! I was going nuts. I then tweaked it with a lot of pauses, slowed the execution, etc. - with no joy.
But then I found it was my startup sequence that did it. If I got an error, the error would show again in a few minutes, unless I did this simple sequence. I now do it every time and it’s been several days with my code running 12 hours+. I then stop it manually and restart it with the same below sequence…
- close UI.Vision RDP
- Chrome > Manage extension (right click on UI icon) > disable, then enable
- open UI.Vision RDP
- refresh every tab; return to tab=0
- start macro
it works every time
2 Likes
Interesting. This points to something not getting cleared correctly.
Over the last 2-3 weeks I’ve started to get this error again. Not very often, but it’s surfaced again. The code stops during an executeScript command and is not immediately after a tab change.
The only clue I have is that I find another tab has a ‘no internet’ warning screen on it. But I can’t say that accounts for every occassion.
When I am checking the browser tabs there is no internet problem (presumably it was brief) and I can refresh the tab
It’s easy to replicate. Disconnect internet and reload tab. I get a #101 error. The ‘no internet’ is a blank chrome page with nothing to detect by my ui.vision script. Is there any way forward with this type of scenario?
The executeScript command runs inside the website, so it fails on the Chrome internal “no internet” page.
Can you use executeScript_Sandbox instead?
You could also switch to desktop automation and detect an image of the dinosaur, then make the macro wait until the internet is back again?
I tried the opening sequence described by PT7. Works longest this way. Crashes everytime after a few hours as UI Vision asks to reload the page with a chrome error of “5” so I can’t tell what the uivision error was. Currently trying to counter this by running the script in local storage mode on one profile, and then using a separate chrome profile in local browser mode to hopefully automate PT7’s opening sequence again. Convoluted but this issue is so important to resolve any way possible.
I’ve been using the built-in API so now I have a way of monitoring the runtime of the uiv… Additionally for large runs of macros I can, per folder of macros run the uivision to restart fresh on the api request. Reliability of large automation runs is solid of many macro folder projects. My use has been for many test suites of macros for QA testing. If you have a macro run for many hours then I doubt you will achieve macro run reliability.
Just me, I was having this problem and I found that if I only closed RPA when I wanted to end the session (meaning close the browser too) - it got rid of 99% of the issues trying to find the browser/tab (being disconnected from RPA). So basically, I do not close RPA until the end of the running dozens of macros (some of the repeated many times) during the session. When I was having problems, I was closing RPA after each macro and leaving the browser open, then run the next macro, closing RPA after the macro, etc.