Ui.Vision RPA Chrome extension: Migration from Manifest V2 to Manifest V3

Known issue #3: Cannot read properties of undefined (reading ‘toPlay’)

Known issue #4: verifyElementPresent hangs if element is not in page

Reporting an issue
Updated on Dec 20, 8 AM EST.
Win 10, Chrome ()
About the macro

  • Running macro in Incognito mode
  • At the end of the macro, invoking “deleteAllCookies” command
  • Browser is closed after the execution [selectWindow | TAB=CLOSE]

The issue:

  • First execution of any macro - successful
  • If i am running same macro second time , Error #101: UI.Vision RPA is not connected to a browser tab"
    After manually restart browser, macro runs again

Hi @Eltal - do you use the LOOP button to play the 2nd macro?

i am talking about same macro.
I am in the middle of the development. Each time i am making change and need to rerun, i need to restart browser

One more thing, the first page that my macro opens, is a text file. Reading data from it for a test

Can you please post a test macro for us? Or provide a video of the issue, so that we can recreate the problem here?

1 Like

Not able to upload, as i am a new user, u r not allowing new user upload files

@Eltal I changed your “trust level”, now the file upload should work.

@Eltal Thanks. And the same macro works OK in V6.2.8?

sure did worked fine

Thanks a lot for the video. That was helpful! It shows that with the 2nd run the OPEN command fails because of the toPlay error. And because of this, the web page is not loaded. And because of this, you get the “can not connect” errors next. We will fix this asap.

The new V6.3.2 solves all bugs reported in this thread. Of course, if you still find problems, please keep reporting them here.

Unfortunately new issues have been discovered.

Edit: This issue is fixed with V6.3.3.

Meanwhile another problem has been discovered: V6.3.1 and V6.3.2 suffer from a memory leak. It shows “only” if you run macros in a loop for a long time. Memory usage increases and at some point the extension crashes.

Reports about this here:


  • One workaround is to go back to V6.2.8 until the issue is fixed (see above).
  • Another solution is to use external looping via the command line. The command line is the best method for 24x7 non-stop automation anyway, as it also avoids browser memory issues.

Screenshot of the memory leak:

The new V6.3.3 solves all bugs reported in this thread. Of course, if you still find problems, please keep reporting them here.

It happened on 6.3.3

1 Like

it was fine in the first few day, then all the problems came back. RUN_TEST_CASE, No tab with id. This is quite stress.

If you have problems with V6.3.3, please try the new V7.0.5 Beta version here:

With V7.0.5 the transition to manifest V3 is completed, the “only” thing left to do is finding and fixing bugs. So if you spot any bugs, please let us know and report them in the forum.