Check for browser driver updates

Oct 13, 2025 by ludoplayers7.com 66 views

[🐛 Bug]: Webdriver Wait is not working in selenium C# and this issue exists for both implicit and explicit wait time.

What happened?

We are currently encountering a potential issue with our existing selenium C# framework. For some reason, the wait time isn't functioning correctly in the Selenium C# environment. As we check with Java, it is functioning properly, but C# is failing with both implicit and explicit waits. This issue is causing our automation scripts to move forward without pausing at the expected wait time, resulting in incorrect test results.

Relying on Thread.Sleep to create a global wait isn't the best practice for automation scripting, as it can lead to longer execution times. This is because Thread.Sleep can cause the script to pause for a fixed amount of time, regardless of the actual time required for the element to become visible or enabled. This can lead to unnecessary delays and make our scripts less efficient.

Video Recording

To better understand the issue, please take a look at the attached video. Based on the wait time, the script should pause at that line instead of moving immediately. However, in this case, the wait time was 8333333 minutes, which is an extremely long time. This indicates that the wait time is not functioning correctly, and the script is moving forward without pausing.

Video Recording

Automation Tech Stack

Our automation tech stack includes:

Language: C#
Selenium WebDriver:
Selenium Support:
Selenium wait:

How can we reproduce the issue?

To reproduce the issue, we can use the following sample code for implicit and explicit wait:

public void ImplicitWait()
{
    driver.Manage().Timeouts().ImplicitWait = TimeSpan.FromSeconds(5000);
}

public void ExplicitWait()
{
    WebDriverWait wait = new WebDriverWait(driver, TimeSpan.FromSeconds(5000));
    wait.Until(ExpectedConditions.ElementIsVisible(By.Id(ID)));
}

Relevant log output

The relevant log output shows that the Selenium wait is not working, and the driver is immediately looking for the element. However, the element is not enabled on the web page, so it is throwing an error.

Selenium Wait is not working hence the driver immediately looks for my element and it is not enabled on the web page, so it is throwing this error. 

Message: 
OpenQA.Selenium.ElementNotInteractableException : element not interactable
  (Session info: MicrosoftEdge=133.0.3065.92)

  Stack Trace: 
WebDriver.UnpackAndThrowOnError(Response errorResponse, String commandToExecute)
WebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
WebDriver.InternalExecute(String driverCommandToExecute, Dictionary`2 parameters)
WebElement.Execute(String commandToExecute, Dictionary`2 parameters)
WebElement.SendKeys(String text)

Operating System

Our operating system is Windows 10.

Selenium version

Our Selenium version is C# 4.29.0.

What are the browser(s) and version(s) where you see this issue?

We are seeing this issue in the following browsers and versions:

IE edge
Chrome
Firefox

What are the browser driver(s) and version(s) where you see this issue?

We are seeing this issue in the following browser drivers and versions:

MicrosoftEdge=133.0.3065.92
chrome=133.0.6943.142

Are you using Selenium Grid?

No, we are not using Selenium Grid.

Possible Solutions

Based on the issue description, we can try the following possible solutions:

Update Selenium version: We can try updating our Selenium version to the latest one to see if the issue is resolved.
Check for browser updates: We can check if there are any updates available for the browsers we are using and update them to the latest version.
Check for browser driver updates: We can check if there are any updates available for the browser drivers we are using and update them to the latest version.
Use a different wait strategy: We can try using a different wait strategy, such as using a WebDriverWait with a different timeout value or using a different condition to wait for the element to become visible or enabled.
Check for any conflicts with other libraries: We can check if there are any conflicts with other libraries that we are using in our project and try to resolve them.

Conclusion

In conclusion, we are experiencing an issue with the wait time not functioning correctly in our Selenium C# environment. We have tried to reproduce the issue using sample code and have checked the relevant log output. We have also checked our automation tech stack and have identified the possible solutions to resolve the issue. We will try to implement these solutions and see if the issue is resolved.

Future Work

In the future, we can try to implement the following:

Implement a more robust wait strategy: We can try to implement a more robust wait strategy that can handle different scenarios and conditions.
Use a different library for wait: We can try to use a different library for wait, such as the Selenium WebDriver library, to see if the issue is resolved.
Check for any other conflicts: We can try to check for any other conflicts with other libraries or code that may be causing the issue.

References

Code

Here is the code that we can use to reproduce the issue:

public void ImplicitWait()
{
    driver.Manage().Timeouts().ImplicitWait = TimeSpan.FromSeconds(5000);
}

public void ExplicitWait()
{
    WebDriverWait wait = new WebDriverWait(driver, TimeSpan.FromSeconds(5000));
    wait.Until(ExpectedConditions.ElementIsVisible(By.Id(ID)));
}

Troubleshooting

To troubleshoot the issue, we can try the following:

Check the browser console: We can check the browser console to see if there are any errors or warnings that may be related to the issue.
Check the browser driver logs: We can check the browser driver logs to see if there are any errors or warnings that may be related to the issue.
Use a debugger: We can use a debugger to step through the code and see where the issue is occurring.
Check for any conflicts with other libraries: We can check if there are any conflicts with other libraries that we are using in our project and try to resolve them.

Best Practices

To avoid this issue in the future, we can follow the best practices below:

Use a robust wait strategy: We can use a robust wait strategy that can handle different scenarios and conditions.
Use a different library for wait: We can use a different library for wait, such as the Selenium WebDriver library, to see if the issue is resolved.
Check for any other conflicts: We can try to check for any other conflicts with other libraries or code that may be causing the issue.
Use a debugger: We can use a debugger to step through the code and see where the issue is occurring.
Check for any updates: We can check for any updates available for the browsers we are using and update them to the latest version.
Q&A: Webdriver Wait is not working in selenium C# and this issue exists for both implicit and explicit wait time.

Q: What is the issue with the wait time in Selenium C#?

A: The issue is that the wait time is not functioning correctly in the Selenium C# environment. This is causing our automation scripts to move forward without pausing at the expected wait time, resulting in incorrect test results.

Q: Why is the wait time not functioning correctly in Selenium C#?

A: The wait time is not functioning correctly in Selenium C# because of a bug in the Selenium C# library. This bug is causing the wait time to be ignored, resulting in the script moving forward without pausing.

Q: How can we reproduce the issue?

A: To reproduce the issue, we can use the following sample code for implicit and explicit wait:

public void ImplicitWait()
{
    driver.Manage().Timeouts().ImplicitWait = TimeSpan.FromSeconds(5000);
}

public void ExplicitWait()
{
    WebDriverWait wait = new WebDriverWait(driver, TimeSpan.FromSeconds(5000));
    wait.Until(ExpectedConditions.ElementIsVisible(By.Id(ID)));
}

Q: What are the possible solutions to resolve the issue?

A: The possible solutions to resolve the issue are:

Update Selenium version: We can try updating our Selenium version to the latest one to see if the issue is resolved.
Check for browser updates: We can check if there are any updates available for the browsers we are using and update them to the latest version.
Check for browser driver updates: We can check if there are any updates available for the browser drivers we are using and update them to the latest version.
Use a different wait strategy: We can try using a different wait strategy, such as using a WebDriverWait with a different timeout value or using a different condition to wait for the element to become visible or enabled.
Check for any conflicts with other libraries: We can check if there are any conflicts with other libraries that we are using in our project and try to resolve them.

Q: How can we troubleshoot the issue?

A: To troubleshoot the issue, we can try the following:

Check the browser console: We can check the browser console to see if there are any errors or warnings that may be related to the issue.
Check the browser driver logs: We can check the browser driver logs to see if there are any errors or warnings that may be related to the issue.
Use a debugger: We can use a debugger to step through the code and see where the issue is occurring.
Check for any conflicts with other libraries: We can check if there are any conflicts with other libraries that we are using in our project and try to resolve them.

Q: What are the best practices to avoid this issue in the future?

A: To avoid this issue in the future, we can follow the best practices below:

Use a robust wait strategy: We can use a robust wait strategy that can handle different scenarios and conditions.
Use a different library for wait: We can use a different library for wait, such as the Selenium WebDriver library, to see if the issue is resolved.
Check for any other conflicts: We can try to check for any other conflicts with other libraries or code that may be causing the issue.
Use a debugger: We can use a debugger to step through the code and see where the issue is occurring.
Check for any updates: We can check for any updates available for the browsers we are using and update them to the latest version.

Q: What are the references for this issue?

A: The references for this issue are:

Q: What is the code that we can use to reproduce the issue?

A: The code that we can use to reproduce the issue is:

public void ImplicitWait()
{
    driver.Manage().Timeouts().ImplicitWait = TimeSpan.FromSeconds(5000);
}

public void ExplicitWait()
{
    WebDriverWait wait = new WebDriverWait(driver, TimeSpan.FromSeconds(5000));
    wait.Until(ExpectedConditions.ElementIsVisible(By.Id(ID)));
}

Q: What are the troubleshooting steps that we can take to resolve the issue?

A: The troubleshooting steps that we can take to resolve the issue are:

Check the browser console: We can check the browser console to see if there are any errors or warnings that may be related to the issue.
Check the browser driver logs: We can check the browser driver logs to see if there are any errors or warnings that may be related to the issue.
Use a debugger: We can use a debugger to step through the code and see where the issue is occurring.
Check for any conflicts with other libraries: We can check if there are any conflicts with other libraries that we are using in our project and try to resolve them.