I run daily scheduled command line scripts using multiple different browsers. After the recent upgrade, 2 of the browsers are no longer working. The browsers open and the UI.Vision Macro opens and the first line (which is just a pause) gives this error:
[error]
until: pendingPlayingTab reset expired!
Once it gets the error, it gets it EVERY time the command line script for that browser runs and the macro does nothing. The only way I have found that I can fix it is to remove the extension and add it again. This fixes it for a random amount of time, and then it fails again and then it is broken. But only for command line starts, if I manually start the macro it runs fine. Also, if I run the macro from the window it failed in it runs fine.
I was going to go to the older version, but it requires changing the install for XModules and I have other browsers that are working. Not sure what else to try at this point?
@ulrich No, it is not 2 macros. All macros started from command line in 2 different browsers fail (they work if started manually from the GUI or even if I click play after it has failed from command line).
I also have macros running from command line in 2 other browsers that don’t have this issue. The only difference I can think is these 2 are set to desktop mode for vision. I can’t set it to not use desktop as these macros need to click outside the window once!
Reinstall of the new version of the extension did not help. It worked for a while and failed again and now all are failing.
Also weird, if I play the macro after it fails, the next run works.
@admin The 2 browsers are chrome based, but not chrome. One is Canary and the other is Comodo Dragon.
The script runs fine in my browser too, but it runs it multiple times. And at some point decides that it isn’t happy anymore and gives the pendingPlayingTab reset expired! on the first line of any macro that is started from command line. If I manually click play at this point it runs, and then next few runs work as well.
I also have Chrome and Edge and Chromium running the same, and they haven’t had an issue yet. The only difference is the 2 that are failing use “Desktop” vision mode.
One thing is, that I time box the macro runs in the command line. This means that sometimes it kills the browser. With the issues with the open command lately just hanging for the 60 seconds and then failing, I have added error checking for that. I am wondering if killing the browser is what is causing it. Let me give that a try! Nope, tested that and it is still working after.