I'm having an issue with the robot. It's an unattended robot that runs for almost 3-4 hours, and sometimes it fails with the following error. It's important to note that I have a retry mechanism in place that retries the entire flow by reopening Chrome. This is done a maximum of 3 times, but all 3 times it fails with the same error.

I wanted to know if anyone has experienced a similar issue.

OpenQA.Selenium.WebDriverException: unknown error: net::ERR_SSL_PROTOCOL_ERROR (Session info: chrome=116.0.5845.111)

at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)

at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)

at WDG.Automation.Browser.SeleniumBrowser.Navigate(String url)

at WDG.Automation.Browser.BrowserInstance.<>c__DisplayClass36_0.<Navigate>b__0()

at WDG.Automation.Browser.BrowserInstance.HandleStaleElement(Action action, Single timeout)

at WDG.Automation.Browser.WebNavigateCommand.Execute(BrowserContext context)

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at WDG.Automation.Language.CommandInterpreter.<Run>d__12.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at WDG.Automation.Language.ScriptInterpreter.<RunCore>d__17.MoveNext()

Hi Felipe, 

I raised your issue to our team and I just got a response, I will put it below: 

This Issue might be occurring due to a missing Chrome driver or an incorrect version of Chrome driver. You can try this out: 

1) Download the Chrome Driver file:
    If version 115 or higher use - https://googlechromelabs.github.io/chrome-for-testing
    If version 114 or lower use - https://chromedriver.chromium.org/downloads

2) Extract the chromedriver.rar on (in case IBM RPA Client version is different than "23.0.7", just change the last folder name):
    %localappdata%\IBM Robotic Process Automation\packages\23.0.7
* If the folder "packages" or "23.0.7" do not exist, create them manually
* If there is an error message when you replace the file, stating that the file is being used, open the taskmanager go to details, and close the instances of chromedriver.exe running.

Let me know if this helps! 

Thank you, Gabriel.

I was able to resolve the issue by updating the client and performing a fresh installation of Chrome.

Additionally, it seems that the errors occur when Chrome has been running for an extended period of time. Occasionally, there are still failures, but I've mitigated them by increasing the time between retries and restarting Chrome.