Hi Philipp, @qqilihq
in the latest Selenium update, the Chrome version appears to have been updated to 145. However, since this is a beta version, the stable Chrome version on the PC remains at 144 even after updating.
Because the beta version is not applied automatically, I’m unable to upgrade Chrome to 145 at the moment. As this affects many existing workflows, I wanted to ask for your support on how we can best adjust or handle this situation.
Thank you in advance.
ERROR Start WebDriver 4:3673:0:4 Execute failed: Could not start a new session. Response code 500. Message: session not created: This version of ChromeDriver only supports Chrome version 145
Current browser version is 144.0.7559.133 with binary path C:\Program Files\Google\Chrome\Application\chrome.exe
Chrome 145 is indeed still in what they call “early stable” state, which means that it’s only rolled out to a small fraction of users - unfortunately the new driver version slipped into the release, which was not intended.
Version 5.13.1 which will be available within the hour fixes this!
Usually, this happens because Chrome is on version 120+ and the driver is still on an older build. If the bundled driver in the Selenium nodes hasn’t caught up yet, manually downloading the ‘ChromeDriver’ and selecting the file path in the node configuration usually clears this right up.
The provided driver in v5.13.0 of the nodes was for 145, which is at the current point in time not widely available - as mentioned due to “early stable” state. So it was not older, but newer. We rolled back to 144 in v5.13.1
I do not recommend to manually fiddle with the driver (but this can be done via the preferences, not the node configuration)
Instead I recommend #q32 from the FAQ as linked above