This exception is thrown when the script attempts to access an object that does not exist. The object may not exist for a variety of reasons. The most common reason is that the object was incorrectly identified. In order to resolve this issue, navigate to the page that caused the error in the script recorder, click 'View' in the Menu and click 'Element HTML' menu item. A window like the following will appear. Hover the cursor over the element in question to determine alternative attributes to use to identify the element.



To determine which attributes are available for the element, refer to this link. To determine possible reasons refer to the following:

1. Cookies were not cleared before recording.

Cookies retain the state of the user for certain sites. For example, it may keep a user logged in during recording but on playback, the browser is no longer logged in.If this is the case, goto the 'Tools' menu and click 'Clear Cache' and re-record.

2. The page has changed since you recorded the transaction.

Occasionally, a page may display ads or another intermediate page. If this is the case, it is recommended that the script is recorded for a transaction that does not often change.If that is not possible, refer to the 'Help' documentation on how a script can be modified to be more resilient to change or contact our support team for further assistance.

3. The page is very dynamic and uses advanced javascript

When web sites use methods to enhance user experience such as AJAX or any type of javascript effect to modify the DOM, additional wait statements must be added in order for the script to know when to execute the next statement. If text is added to the page as a result of these effects, highlight the new text with the cursor and right click, then click 'add wait_until'.

4. An action in the script caused multiple steps to be recorded.

While recording, if multiple steps are created for one action, the javascript on the page may have caused another event to be recorded by the script recorder. If this is the case, removing the extra step may resolve your issue.

5. Your website has very dynamic content

If your site has content that is constantly changing, it may be difficult to create a reliable script for your site. Using the index attribute to identify an element may not work on playback. If this is the case, our Support Team would be happy to work with you and and create a script for your transaction.

This is the most common error when scripting. We strongly recommend reading the 'Tips and Tricks' and the 'Help' documentation in order to troubleshoot the problem.

This exception is thrown when the script attempts to modify an object in the page that has been disabled. To resolve this issue, simply remove the line in the script that causes this error. The state of the object is disabled and therefore the script cannot interact with it.

This error occurs when the script tries to access a frame that does not exist. To resolve this issue, the correct attributes identifying the frame must be identified.

To determine the frame path to an element on an HTML web page, use the 'Element HTML' option from the 'View' menu. If an element is displayed inside a frame, the Element HTML textbox will display this frame path.

To determine which attributes are available for the frame element, refer to this link.

Possible Reasons:

1. Cookies were not cleared before recording.

Cookies retain the state of the user for certain sites. For example, it may keep a user logged in during recording but on playback, the browser is no longer logged in.If this is the case, goto the 'Tools' menu and click 'Clear Cache' and re-record.

2. The page containing the element is not the same during playback.

Occasionally, a page may display ads or other intermediate page. If this is the case, it is recommended that the script is recorded for a transaction that is the same every time.

This error will occur when the script contains a command to interact with an input that has been specified as belonging to a specific form. Upon playback, this form could not be identified. To resolve this issue, it may be necessary to view the source of the page to determine which form contains this input.

To determine which attributes are available for the form element, refer to this link.

This error will occur when the script tries to change the value of an element that has been declared as read only in the HTML page. A common element that is declared read only is the text field element.

To resolve this error, the command that sets the value of the read only field must be removed from the script.

This error will occur when the script attempts to access a table cell that does not exist. This can happen for a variety of reasons. The common reasons are that the table has been incorrectly identified or that the rows and cells are indexed starting at 0 instead of 1.

Remember that the row and table cells are indexed starting at 1. For example, the first row of a table is index 1; the first cell of that row is also indexed 1.

This error occurs when the script tries to attach to a window that does not exist. This can occur for a variety of reasons including having a popup blocker enabled or if window was slow to appear due to slow connectivity.

If this occured because of "popup blocker" software installed on the client machine, simply disable the popup blocker and allow this window to open when required.

If this occurred because of "connectivity" issues, it may be necessary to explicitly tell the script how long to wait before erroring. To do this, add the following line before the attach command in the script:


Where 'x' is the maximum number of seconds the script should wait before erroring.