What should I do if I get the error "Unable to locate an element on a page"?

At times, some page elements can't be located due to network issues or loading issues. There are two methods of fixing the error: you can either check the root cause analysis (RCA) screenshot or you can edit the web script.

To fix the error by editing the web script:

1. Log in to Site24x7.

2. Navigate to Home > Monitors.

3. Click the monitor of your preference.

4. On the Monitor Status page that opens, click the hamburger icon next to the monitor name and click Edit Web Script.
   

5. In the script that opens, add lines in the following format with appropriate values above the page elements that are unable to be located:
   

          
         

wait(<time in milliseconds>)

wait_for_element_presence(<element type>,<element name>,<maximum wait time in seconds>)
wait_for_element_visibility(<element type>,<element name>,<maximum wait time in seconds>)      

         For example, in the case of an XPath element, this is the format:
     

  wait("1000")
  wait_for_element_presence("xpath",".nav__inner .site-nav__spacer__top-handheld","40")
  wait_for_element_visibility("xpath",".nav__inner .site-nav__spacer__top-handheld","40")

          

Edit web script

• Related Articles

• How to configure the NGINX status page for monitoring NGINX performance

  The NGINX plugin uses the NGINX status page to pull the performance metrics of the NGINX server. You may encounter the following errors while installing the NGINX plugin integration: Error_code : HTTP Error 404: This error usually indicates that the ...

• API exceeded error

  Why do I get an API exceeded error after a few attempts? Every API has a certain limit to the number of requests a user can hit within a period of time, called the rate limit. An error message is triggered when a user does one of the following ...

• Troubleshoot "[Errno 111] Connection refused" error when installing Tomcat plugins

  When installing Tomcat plugins, you may encounter the following error: We failed to reach a server. Reason: [Errno 111] Connection refused: This error indicates that your client is unable to establish a connection to the Tomcat Manager URL, but the ...

• Unable to see application after adding APM Insight .NET agent and getting "Failed to Load Profiler" error

  The following are few reasons that might pose an interference with the APM Insight .NET agent profiling: 1. User Permission settings 2. Competing profilers/monitoring services If the installation is not done with administrative privileges, the ...

• Troubleshoot Error 404, Error 111, and "no host given" error when installing the Apache plugin

  When installing the Apache monitoring plugin, you may encounter the following errors: Error_code : URL Error no host given: The "no host given" error message typically indicates an issue with a URL or request that lacks a hostname. If you encounter ...