Skip to main content
D
dwilks73
Cadet | Tier 2
January 24, 2024
Solved

Chrome Update 121.0.6167.86 Issues

  • January 24, 2024
  • 22 replies
  • 1373 views

Since Chrome has updated most of our bots no longer work.  Any interaction with text fields don’t produce the results we were previously experiencing.  I created a small bot to open Google in Chrome and enter a search term for Todays Weather, but that basic bot doesn't even work.  I have attached the bot to this post and was wondering if anyone else is experiencing the same issues?

Cheers

Dwayne

    Best answer by ChanduMohammad

    Hi All,

    Checkout the KB

    22 replies

    Show previous replies
    M
    MichalTurek
    Navigator | Tier 3
    January 30, 2024

    The other issue we experienced is that the new package needed to be applied to > 150 bots, so we used the Update Bot process to update the packages of those bots.  Unfortunately, there is new functionality for setting timeouts when accessing a DOM element using the Recorder and this caused a lot of these bots to require manual updating (as they were using a recorder package without this functionality) so that they were able to work again.

    It would have been preferable if the update process was able to default to Basic and use the value that was previously entered.

    Hallo @dwilks73 

    and that’s what exactly happening, when switching to new package the action takes the previous time as basic value...

    The Basic option is selected and the Wait for system response (in seconds) is blank.  I would have expected that this is filled in with the previous value, but it isn’t, it is blank so the entire bot is invalid due to this. 

    hmh, that’s strange… What package number You\re introducing and are Youc Cloud user or on-prem?

    V
    Varaprasad315
    Cadet | Tier 2
    January 31, 2024

    Short term solution is for critical automations open bot in private tab and go to packages and change recorder version of package from not default to default version. i tried and it’s working now.

    Terms & ConditionsAccessibility statement