Add ERR_NAME_NOT_RESOLVED to the list of errors that force a retry of driver.get(url)
Similar to ERR_CONNECTION_TIMED_OUT, ERR_CONNECTION_CLOSED, and ERR_CONNECTION_RESET, ERR_NAME_NOT_RESOLVED is one of those rare errors that may occur if the target website is having DNS issues, load-balancing issues, etc. A retry of driver.get(url) shortly after the error usually resolves the issue.
Here's the full list of errors that SeleniumBase is built to handle correctly (after this new addition):
Add
ERR_NAME_NOT_RESOLVED
to the list of errors that force a retry ofdriver.get(url)
Similar to ERR_CONNECTION_TIMED_OUT, ERR_CONNECTION_CLOSED, and ERR_CONNECTION_RESET, ERR_NAME_NOT_RESOLVED is one of those rare errors that may occur if the target website is having DNS issues, load-balancing issues, etc. A retry of
driver.get(url)
shortly after the error usually resolves the issue.Here's the full list of errors that SeleniumBase is built to handle correctly (after this new addition):
ERR_CONNECTION_TIMED_OUT
ERR_CONNECTION_CLOSED
ERR_CONNECTION_RESET
ERR_NAME_NOT_RESOLVED
Timed out receiving message from renderer
cannot determine loading status
unexpected command response