> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/error-logs.md). # Error Logs Error Logs contain the errors that you may encounter while performing automation activities or executing workflows. These logs help you understand what went wrong during the process and assist in identifying and resolving issues more effectively. | Error | Description | Solution | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Dangling | This error occurs when you have used **Get Param** or loops but have not added the **End Loop** statement. | Add an **End Loop** after the **Get Param** or **Start Loop** process ends, once all interactions are completed. | | 77 Error with database operation | This error occurs when you have used **Run Query**(DB) and you have not provided the valid connection details. | Provide the correct connection details, **\;\;\;\;\;\;\;\(Optional);\(Optional)** | | Forbidden request, Connection refused, please configure server ip and server port in Edit-> configuration, and retry. | This error occurs when Server Address is not provided in the configuration section of Avo Assure Client | Provide the correct server IP address for the field Server Address in the configuration section of Avo Assure Client | | Data parameterization failed: Wrong datatable name/ file name/ Sheet name given, please check and provide valid one. | This error occurs when wrong datatable name or file name or sheet name is given. | Provide the correct datatable name or file name or sheet name. | | File path not set | This error occurs when the path of file is not provided for the **Set Path for File** action. | Provide the path of file. | | Avo Integrator Extension Required | This error occurs when attempting to log in to **Test Management** integrations (such as Jira, Azure DevOps, etc.) without having the **Avo Integrator** Extension installed in the browser. | Install and enable the **Avo Integrator** Extension in your browser. | | if: Expression must be enclosed within "(" and ")" | This error occurs when the input value didnʼt follow the correct syntax format and does not provide parentheses **()** for the **if** condition. | Ensure that the condition is always enclosed within parentheses and the correct syntax should be provided | | ERR\_CUSTOM\_VERIFYEXIS TS: Previous step verify exists is missing | This error occurs when **VerifyExists** is not added as a previous test step for using **@Custom** Element. | Ensure that the **VerifyExists** is added as a previous test step, while using **@Custom** element. | | Invalid Input : Check with Variable Input Value or Value Input 1 | This error occurs when **Create Dynamic Variable** name is not enclosed within curly braces **{}**. | Ensure that the **Create Dynamic Variable** name is enclosed within curly braces **{}**. | | Error getting line number in .xlsx : Excelname.xlsx | This error occurs when **Verify Content** is executed against an Excel file and the specified worksheet name does not exist. | Verify the worksheet name in the Excel file and provide the exact sheet name in the input value. | | \[WinError 2] The system cannot find the file specified | This error occurs when the **Execute File** action is configured with a file name or file path that does not exist on the execution machine. | Verify that the file exists in the specified location before execution. | | Navigation failed, wrong URL format | This error occurs when an invalid URL is provided in the **Input Value** column of the **Navigate to URL** action. | Provide vaid web address to perform **Navigate to URL** action. | | Invalid Input: Only numbers are allowed | This error occurs when a non-numeric value is provided in the **Input Value** column of the **Wait** action. | Provide only a numeric value. | | Wrong filters given, please check and provide correct one | This error occurs when an invalid row range format is specified in the **Get Param** action. | The row range should follow the supported format **\.** | | Invalid Input for **Evaluate** Action | An **Evaluate** expression attempted division by zero. | Validate the denominator before performing division. | | Invalid Credentials for **JIRA Integration** | Avo Assure could not authenticate to JIRA for mapping cases or logging a defect. |
  • Verify the JIRA base URL and API token.
  • Confirm that the account has project access.
  • Re-authenticate and retry.
| | Scheduled execution did not trigger | A scheduled run did not start (Avo Agent offline at scheduled time or wrong time zone). |
  • Confirm that the Avo Agent is online at the scheduled time.
  • Verify the schedule of time and time zone.
  • Re-save the schedule.
| | Browser driver version mismatch | The installed browser version doesn't match the driver on the execution machine. |
  • Check the browser version on the execution machine.
  • Update the browser or matching driver in Avo Assure Client folder path
    (Avo Assure> Lib > Drivers)
  • Restart the Avo Assure Client.
| | **Keyword Not valid** (**Custom Action**) Custom Keyword Exception | A **Custom Action** contains a script error (JavaScript or Python) or a missing parameter. |
  • Open the Custom Action and review the code.
  • Fix syntax errors and confirm all inputs are passed.
  • Save and re-run.
| | Invalid Input for **Get File Content** (PDF) | This error occurs when the input value for the **Get File Content** action on a PDF file does not follow the correct syntax. For example, a missing or invalid file path, page number, start/end string, or content type. |
  • Provide the input in the correct format: \;\;\;\;\.

Ensure the file path is valid and accessible, the page number is numeric, the start and end strings exist in the document, and the content type is text, image, or all.

| | **LaunchApplication**(**SAP**): The given window name is not found | This error occurs when the **Launch Application** action is used for SAP, the window name & path provided in the **Input Value** column does not match the actual SAP application window and path. | Provide the correct application path and window name in the format:**\; \** (e.g., C:\Program Files (x86)\FrontEnd\SapGui\App.exe; SAP Logon 760).Ensure the executable path is valid on the execution machine and the window name matches the SAP window exactly. | | **SAP ServerConnectError occured** : Given Server discription is incorrect, (-2147352567, 'Exception occurred.', (614, 'saplogon', 'The enumerator of the collection cannot find an element with the specified index.', 'C:\Program Files (x86)\SAP\FrontEnd\SapG ui\saplogon.HLP', 393215, 0), None) | This error occurs when the **Server Connect** action is used for SAP and the server description provided in the **Input Value** column does not match any entry in the SAP Logon connection list. |
  • Provide the correct SAP server description exactly as it appears in the SAP Logon connection list (e.g., the connection/system name shown in SAP Logon).

Ensure the entry exists in SAP Logon on the execution machine, and the name matches exactly, including spacing and case. For example: SAP HANA

| | Row or Column value exceeds the limit specified (22/80) | This error occurs when Avo Assure attempts to position the cursor at a row or column that exceeds the maximum supported limit for the target application. Since the specified position is invalid, the cursor cannot be placed. | Verify that the row and column values are within the supported range of the application before executing. | | Text not found | This error occurs when Avo Assure attempts to locate or verify the specified text in the application, but the expected text is not present. As a result, the verification fails. | Verify that the expected text is correct, ensure the application has loaded the required content, and retry the verification. | | Inputs do not match | This error occurs when Avo Assure compares two input values and finds that they are different. Since the values do not match, the verification returns a **False** status. | Verify both the expected and actual input values and ensure they match before performing the verification. | | Please provide valid date | This error occurs when an action receives a date that is invalid or not in the expected format. Since the date cannot be processed, the operation fails. | Provide a valid date in the required format supported by the action and verify that the value represents a valid calendar date. | | Display Timeout cannot be less than or equal to 0 | This error occurs when a display timeout value of **0** or a negative number is provided. Since timeout values must be greater than zero, the action cannot be executed. | Specify a timeout value greater than **0** before executing the action. | | Invalid Input: No content found in the specified location | This error occurs when Avo Assure attempts to retrieve content from the specified location, but no data is available. As a result, the requested operation cannot be completed. | Verify that the specified location contains the required content and ensure the input path or source is correct. | | Image operations do not support 8-bit or 32-bit depth images | This error occurs when an image operation is performed on an image with an unsupported color depth. Since the image format is not supported, the operation cannot continue. | Use an image with a supported bit depth or convert the image to a compatible format before executing the action. | | Invalid input, hence **Evaluate** method failed | This error occurs when the **Evaluate** action receives invalid or incomplete input. Since the expression cannot be evaluated, the action fails. | Verify that the expression is valid, complete, and follows the required syntax before executing the Evaluate action. | | Input/Output value exceeds seventeen digits | This error occurs when the input or calculated output exceeds the maximum supported precision of **17 digits**. As a result, the **Evaluate** action cannot process the value. | Reduce the input size or precision so that the value remains within the supported **17-digit** limit. | | Invalid XML format | This error occurs when an XML input or file contains invalid syntax or an incorrect structure. As a result, Avo Assure cannot parse the XML content. | Validate the XML structure, correct any syntax errors, and ensure the XML is wellformed before retrying the operation. | | Variable does not exist | This error occurs when an action attempts to access a dynamic variable that has not been created or initialized. Since the variable is unavailable, the action cannot retrieve its value. | Verify that the variable is created before use and ensure the variable name is spelled correctly. | | Variable already exists | This error occurs when an attempt is made to create a dynamic variable with a name that already exists. Since duplicate variable names are not allowed, the creation fails. | Use a unique variable name or update the existing variable instead of creating a duplicate. | | XML file doesn't contain tag names | This error occurs when Avo Assure attempts to read an XML file that does not contain valid XML tags. Since the required tag structure is missing, the operation cannot be completed. | Verify that the XML file contains valid tag names and follows the expected XML structure before executing the action. | | Excel sheet should contain unique column names | This error occurs when an Excel sheet contains duplicate column names. Since Avo Assure cannot uniquely identify the columns, the data retrieval operation fails. | Rename duplicate column headers so that every column has a unique name before using the Excel sheet. | | Excel sheet doesn't contain column names | This error occurs when Avo Assure attempts to retrieve data from an Excel sheet that does not contain column headers. Since column names are required for data mapping, the operation fails. | Ensure that the first row of the Excel sheet contains valid column names before executing the action. | | Unable to launch the application | This error occurs when Avo Assure fails to start the specified application. This may happen due to an incorrect application path, missing executable, insufficient permissions, or application compatibility issues. | Verify the application path, ensure the executable exists, confirm sufficient permissions, and check that the application is compatible with the operating system. | | Tooltip text not available | This error occurs when Avo Assure attempts to retrieve the tooltip text of an element, but no tooltip is available or displayed for that element. | Verify that the element contains a tooltip and ensure the pointer is positioned correctly to display it before retrieving the value. | | File doesn't exist | This error occurs when Avo Assure attempts to access a file that cannot be found at the specified location. Since the file is unavailable, the requested operation cannot be completed. | Verify that the file path is correct, ensure the file exists at the specified location, and confirm that it has not been moved or deleted. | | **JumpBy** for negative step number is not allowed | This error occurs when the **JumpBy** action is given a step value that exceeds the available range of the target element/collection. | Provide a valid **JumpBy** step value that stays within the available range. Verify the total count/range of the target before setting the **JumpBy** value. | | Email Notification Failed | Automated email notifications could not be sent after execution. | Verify email server configuration, SMTP settings, credentials, and network connectivity. | | User Account Locked | The user account has been locked due to multiple unsuccessful login attempts with incorrect credentials. As a security measure, the user will be prevented from accessing Avo Assure until the account is unlocked. | Only users with Admin privileges can unlock the account. Navigate to **Admin ab**> **Session Management**, locate the locked user account, and perform the unlock operation. The user can then log in again using valid credentials. | | Request Payload Error | Request body contains invalid or incomplete data. | Correct the payload structure and mandatory fields. For example: Even a small structural change needs validation. | | Invalid Endpoint URL | API endpoint URL is malformed or inaccessible. | Verify the endpoint URL and network connectivity | | **Action Not Recognized**after Element identification | The element is successfully identified during execution, but the action fails with an **Action Not Recognized** error. This commonly occurs when navigation elements are captured using labels or unstable identification properties that do not accurately represent the interactable object. | Open the element properties and prioritize a more reliable locator strategy, such as a Relative XPath, CSS Selector or Recapture or update the element, if necessary, then re-execute the test case to validate the interaction. | | Value Does Not Exist | The **Select Value By Text** action fails when the input text does not exactly match any of the available options in the dropdown or list control. As a result, the specified value cannot be located and selected during execution. | Verify that the input value exactly matches the text displayed in the dropdown or list, including spaces, special characters, and case sensitivity where applicable. Update the input value and re-execute the test case. | | Migration to Avo -Invalid ZIP File Name | This error occurs while importing automation assets using the **Migration to Avo** feature when the uploaded ZIP file does not follow the required naming convention. Avo Assure validates the file name before processing the migration. | Rename the ZIP file to **selenium\_testcase\_batch.z ip** before uploading it. Ensure the file follows the required naming convention and retry the migration. | | Failed to Open Local File for Key **file** | This error occurs while working with **Form Data** requests in API when attempting to upload a file. The error is typically encountered when the specified file path is invalid, the file does not exist, or the file content cannot be accessed. | Verify that the file path is correct, ensure the file exists at the specified location, and confirm that the file is accessible. Update the request with the correct file path and retry the operation. | | Screenshot Not Available | This error occurs when viewing execution reports or downloading a PDF with screenshots, but the screenshots are unavailable. It is commonly encountered when the **Avo Assure Instance** and the **Avo Assure Client** are running on different machines, preventing screenshots from being captured and embedded in the report. | Execute the test from the same machine where the **Avo Assure Client** is running or ensure the execution environment is configured to support screenshot capture. **Re-run** the execution to generate reports with screenshots. | | Header Name Invalid or Missing | This error occurs when the request contains an invalid, missing, or unsupported header for the selected request body format (e.g., Raw, Form URL Encoded, or Form Data). As a result, the API rejects the request due to incorrect header configuration. | Verify that the request body format matches the API specification and ensure the appropriate headers (such as Content-Type) are configured correctly. Update the header values based on the selected request format and retry the request. | | You Don't Have Privilege to Perform This Action | This error occurs when a user attempts to perform an action that is restricted by their assigned role. Users with **Quality Engineer** or **Quality Lead** roles may encounter this error when accessing features or administrative functions that require higher-level permissions. | Ensure the user is assigned the **Quality Manager** role or another role with the required privileges. If the action is business-critical, request an Admin to update the user's role and permissions before retrying the operation. | | Unable to Capture Dropdown Element | The dropdown closes automatically when attempting to capture one of its options, preventing the element from being captured successfully. This typically occurs with dynamic or auto-collapsing dropdown controls. | Use the **Delay** option while capturing the element. Configure an appropriate delay (in seconds) to provide sufficient time to open the dropdown and keep it expanded before initiating the capture process. | | Authentication Failed | Authentication fails when the access token used for the API request has expired or is no longer valid. As a result, the API rejects the request and returns an authentication or authorization error. | Regenerate a valid access token by re-authenticating with the API or by using the refresh token (if supported by the API). Update the token in the request and retry the operation. | | Error occurred due to unexpected alert | This error occurs when an unexpected alert or pop-up appears during execution, preventing Avo Assure from interacting with the application. | Handle or dismiss the unexpected alert before continuing execution or add appropriate alert-handling steps in the test case. | | GET Request Contains Invalid Request Body | This error occurs when a request body is sent with a **GET** request to an API that does not support request payloads for GET operations. | Remove the request body from the **GET** request or use the appropriate HTTP method if the API requires a payload. | | Application Window Not Detected During Continuous Capturing | This error occurs when the desktop application window unavailable. | Ensure the application is open during the element capture process to achieve a continuous Capturing Mechanism. | | Index input cannot be 0 for table | This error occurs when a table action is executed using an index value of **0**, which is not supported. Table indexing starts from **1**, so the action cannot be completed. | Provide a valid table index greater than **0** and ensure the specified row or column exists. | | Invalid Action Sequence | This error occurs when steps are arranged incorrectly. | Reorder test steps logically in Test Step Group. | | No Item Matches the Given Query | This error occurs when attempting to retrieve data from an API using a **Path** or **Query** expression that does not match any item in the response. As a result, Avo Assure is unable to locate the requested value. | Verify that the specified **Path** or **Query** expression is correct and matches the structure of the API response. Ensure the response contains the expected data and update the expression if the response structure has changed. | | File type input Element is not Clickable, use**UploadFile** keyword instead | This error occurs when a **Click** action is executed on a file upload control. Since file input elements are not designed to be clicked for file selection, the action fails. | Use the **UploadFile** action instead of the **Click** action to upload files. | | The Current Operation Cannot Be Performed Because of the Object State | This error occurs when Avo Assure attempts to interact with an object before it is fully loaded or ready for interaction due to synchronization delays. |
  • Add an appropriate wait to allow the screen to load completely before performing the action.
  • If required, perform a Click action on the screen or target control to bring the object into an interactive state before retrying the operation.
| | Response Body is Empty | This error occurs when an API request completes successfully, but the response body contains no data. As a result, actions that expect response content cannot proceed. | Verify that the API returns data and that the request parameters, such as **Query** and **Path** parameters, are correct. | | Invalid Key/Missing Key/Block Index in JSON Input | This error occurs when the **Get Key Value** action uses a key, block index, or JSON path that does not exist in the JSON response. As a result, Avo Assure cannot retrieve the requested value. |
  • Verify the JSON structure and ensure that the correct key name, block index, and hierarchy are specified.
  • Update the input to match the actual JSON response, and then run the action again.
| | Invalid Input : YYYY/mm/dd | This error occurs when the **Get Current Date** action uses an unsupported date format string. |

Provide a valid date format in the Input Value field of the Get Current Date action. Supported Date Formats:

  • dd/MMM/yyyy
  • MMM/dd/yyyy
  • dd/MM/yyyy
  • /MM/dd/yyy
| | Variable does not exist - **Modify Variable Value** action | This error occurs when the **Modify Variable Value** action attempts to update a variable that does not exist. |
  • Add a Create Dynamic Variable step before the Modify Variable Value step. Ensure that the variable name inside the curly braces ({}) matches exactly.
  • Ensure that the variable must be created by using the Create Dynamic Variable action before its value can be modified.
| | Invalid For Count | This error occurs when the **For Count** value in a **For Loop** action is not a valid positive integer. Avo Assure requires a positive numeric value to determine the number of loop iterations. If the value is blank, nonnumeric, zero, negative, or contains special characters, the action fails. | Verify that the **For Count** field contains a valid positive whole number, such as 1, 5, or 10. | | Input is Empty, please provide proper input | This error occurs when the **Get Cell Value** action runs on a table or grid element, but the **Input Value** column (Row;Column) is blank. | Ensure that the **Input Value** field for the **Get Cell Value** action uses the correct format: **\;\;\
(optional);\(optional);\(optional);\(optional)**. Provide valid row and column values, such as **2;4;body**, and verify that the specified row and column exist in the target table before running the action. | | No matching row/column found for the given conditions | This error occurs when the **Verify Cell Value** action runs on a table or grid, but Avo Assure cannot find the specified row or column based on the row or column index or the optional row or column attribute filters in the **Input Value** column. | Verify that the row and column values in the **Input Value** field correspond to an existing cell in the target table. If you use row, column, or value attributes, ensure that they exactly match the current table structure and attributes. | | Could not retrieve the current URL. Browser session may be invalid | This error occurs when the **Get Current URL** action runs, but Avo Assure cannot communicate with the browser session to retrieve the current page URL. This error typically occurs when the browser window is closed unexpectedly. | Verify that the browser window launched by Avo Assure is open and has not been closed or crashed during execution. Ensure that no manual action, such as closing tabs or switching windows, disrupts the automation session. | | Unable to open a new browser tab. Possible issue with browser session | This error occurs when the **Open New Tab** action runs, but Avo Assure cannot open a new browser tab in the current session. This issue typically occurs when the browser session crashes, is closed, or loses connection with the WebDriver or browser extension. |
  • Verify that the browser session launched by Avo Assure is active and has not been closed or crashed.
  • Close unnecessary browser tabs or windows to free resources, and ensure that the browser extension or WebDriver is running correctly.
  • If the issue persists, restart the browser session by relaunching the application, and then run the Open New Tab action again.
| | Page refresh failed. The current browser context may be unresponsive | This error occurs when the **Refresh Page** action runs, but Avo Assure cannot reload the current page. This issue occurs if the browser session is unresponsive, the page is stuck loading, the connection to the browser (WebDriver or browser extension) is lost, or the browser tab or window is closed. | Verify that the browser window or tab controlled by Avo Assure is open, active, and responsive. If the browser is frozen or unresponsive, close any stale browser instances using the Kill Stale Process option in the Avo Assure Client, then relaunch the application and retry the operation. | | Date picker control state does not allow to perform the operation. | This error occurs when the **Set Date** action is executed, but Avo Assure is unable to interact with the target date picker control because it is unavailable, disabled, not visible, or otherwise not in an interactable state. | Verify that the date picker control is visible, enabled, and interactable before executing the **Set Date** action. Add an appropriate wait or synchronization step to ensure the date picker has fully loaded and is ready for interaction before retrying the operation. | | Element not found | This error occurs when the captured element cannot be found on the application screen during execution, or when the element's properties have changed, causing Avo Assure to be unable to locate or interact with it. | Verify that the target element is present on the application screen during execution. If the element has changed or cannot be identified, update its object properties in the **Element Repository** and recapture the element if necessary before retrying the execution. | | If condition is invalid | This error occurs when the input value provided to an action does not conform to the required syntax or expected format, preventing Avo Assure from processing the input successfully. | Verify the input syntax and ensure that the values provided match the format expected by the action. Correct any invalid or unsupported input before retrying the execution. | | Permission denied(@Excel) | This error occurs when Avo Assure is unable to access the specified Excel file because it does not have the required permissions, or the file is currently open or locked by another application or user. | Ensure that the Excel file is closed, accessible, and not locked by another application or user. Also, verify that you have the required read and write permissions to access the file before retrying the operation. | | Action click not recognized. | This error occurs when the click action type specified in the test step is invalid or not recognized by Avo Assure, preventing the action from being executed. | Review the test step configuration and ensure that a valid, supported click action type is selected. If necessary, edit the test step and reset the click action to a supported type (for example, Simulate Press Action ), then retry the execution. | | Message: no such window | This error occurs when Avo Assure attempts to interact with a browser window or tab that has already been closed, is no longer active, or whose browser handle is no longer valid. As a result, the requested action cannot be performed. | Ensure that the application window or browser tab is not closed prematurely by a previous test step. Before executing the action, add a step to switch to the correct browser window or tab to ensure Avo Assure interacts with the appropriate window handle. | | Checkbox already Selected/Unselected | This error occurs when the **Select Checkbox** or **Unselect Checkbox** action is executed on a checkbox that is already selected. Since the checkbox is already in the expected state, no additional action is performed, and Avo Assure returns a False status. | Verify whether the checkbox is expected to be pre-selected before executing the **Select Checkbox** or **Unselect Checkbox** action. If the checkbox is already selected and no state change is required, remove the redundant action from the test step before retrying the execution. | | Row number or Column name does not exist | This error occurs when the specified row number or column name cannot be found in the target table or grid. As a result, Avo Assure is unable to locate the requested cell or data, and the operation fails. | Verify that the specified row number and column name are correct and exist in the target table or grid before executing the action. If the table content is dynamic, ensure that the required row and column are available at runtime before retrying the execution. | | Invalid input: the element cannot hold multiple files | This error occurs when Avo Assure attempts to upload multiple files to a file upload control that supports only a single file. Since the control does not allow multiple file selection, the upload operation fails. | Verify whether the file upload control supports multiple file selection. If multiple file uploads are not supported, provide only a single file as input before retrying the operation. | | The Cell value and Expected value do not Match | This error occurs when Avo Assure compares the value of a table or grid cell with the expected value and detects a mismatch. Since the actual cell value does not match the expected value, the verification returns a False status. | Verify that the expected value is correct and ensure that the application displays the expected value in the specified table or grid cell before performing the verification. If the data is dynamic, confirm that the application has fully loaded and the correct data is displayed before retrying the operation. | | Unable to establish connection to DB | This error occurs when Avo Assure is unable to establish a connection to the configured database. This may occur because the database server is unavailable, the connection details are incorrect, or the user does not have sufficient privileges to access the database. | Verify that the database connection details are correct, ensure the database server is running and accessible, and confirm that the user has the necessary permissions to establish the connection before retrying the operation. | | Values does not match | This error occurs when Avo Assure compares the expected value with the actual value obtained during execution and finds that they do not match. As a result, the verification fails and returns a False status. | Verify both the expected and actual values, and ensure that the application contains the correct data before executing the verification. | | Execution Terminated: Jump to test case name not present | This error occurs when the **Jump To Test Case** action references a test case that does not exist or cannot be found. As a result, Avo Assure cannot navigate to the target test case, and the execution is terminated. | Verify that the referenced test case exists and ensure that the test case name is entered correctly before executing the Jump To Test Case action. | | Invalid file | This error occurs when the specified file is invalid, corrupted, or in a format that is not supported by the requested action. As a result, Avo Assure cannot process the file. | Verify that the file exists, is not corrupted, and is in a supported format before executing the action. If the issue persists, ensure that the correct file is selected and accessible. | | The specified file is not an Excel file | This error occurs when an Excel action is executed on a file that is not in a supported Excel format. As a result, Avo Assure cannot process the file. | Ensure that the input file is a valid and supported Excel file (such as .csv or .xlsx) before executing the action. | | Invalid input, JumpBy step doesn't exist | This error occurs when the **JumpBy** action specifies an invalid step number. As the specified step does not exist in the test case, Avo Assure cannot perform the jump operation. | Verify that the specified step number exists in the test case, and provide a valid **JumpBy** value before executing the action. | | Error with database query | This error occurs when the SQL query executed by Avo Assure contains syntax errors, references invalid database objects, or includes unsupported SQL statements. As a result, the query execution fails. | Verify the SQL query syntax, ensure that the referenced database objects exist, and confirm that the query is compatible with the target database before executing the action. | | Error writing to file | This error occurs when Avo Assure attempts to write data to a file but is unable to complete the operation. This may occur if the file is read-only, locked by another application, the file path is invalid, or the user does not have the required write permissions. | Verify that the file is not open or locked by another application, ensure that the file path is valid, and confirm that the user has the required write permissions. Also, verify that the input values match the syntax expected by the action before retrying the operation. | | Input Error: Invalid Sheet name | This error occurs when an Excel action is executed using a sheet name that does not exist or is specified incorrectly. As a result, Avo Assure cannot locate the worksheet, and the operation fails. | Verify that the specified sheet name exists in the Excel workbook. Ensure that the sheet name is spelled correctly, including its case, and provide a valid sheet name before executing the action. | | Element is not displayed | This error occurs when Avo Assure executes the **Get Element Text** action, but the target element is not visible on the page even after waiting for the configured element to load timeout. As a result, the text cannot be retrieved. | Verify that the element is displayed before executing the action, scroll the element into view if necessary, and increase the **element\_load\_timeout** for slow-loading pages. | | Input Text \ mismatched with \ | This error occurs when the **Verify Element Text** action compares the expected input value with the actual text of the element and detects a mismatch. As a result, the verification returns a False status. | Verify that the expected text exactly matches the actual element of text, including spaces, special characters, line breaks, and letter case. | | Invalid Input: \ | This error occurs when the **Verify Element Text** action receives an invalid, empty, or unsupported input value. Since the expected text cannot be evaluated correctly, the verification fails. | Provide a valid expected text value and ensure the input is not empty or incorrectly formatted before executing the action. | | Disabled object error | This error occurs when Avo Assure attempts to execute the **Click Element** action on an object that is currently disabled. Since disabled objects cannot receive user interaction, the action cannot be completed. | Ensure the object is enabled before executing the action. Complete any prerequisite steps required to enable the object or wait until it becomes interactable. | | Element is disabled (Drag and Drop file) | This error occurs when Avo Assure attempts to perform a Drag, Drop, or Drop File action on a disabled target element. Since the element does not accept user interaction, the operation fails. | Verify that both the source and target elements are enabled before executing the action and complete any prerequisite steps required to enable them. | | Source or target element may not be valid | This error occurs when Avo Assure cannot identify or access the source or target element required for the Drag action. As a result, the drag operation cannot be completed. | Verify that both the source and target elements are correctly captured, exist in the current application state, and are visible before executing the action. | | No tool tip text found | This error occurs when Avo Assure executes the **Get Tooltip Text** action, but no tooltip is displayed for the target element. As a result, the tooltip text cannot be retrieved. | Verify that the element displays a tooltip on hover, ensure the mouse pointer remains over the element until the tooltip appears. | | No valid locator found in objectname (Wait Element to be visible) | This error occurs when the **Wait For Element Visible** action cannot identify the target element because no valid locator is available in the Element Repository. As a result, Avo Assure cannot wait for the element to become visible. | Verify that the element has at least one valid locator property, update or recapture the object if necessary, and ensure the locator correctly identifies the element. | | Delay Timeout Exceeded | This error occurs when the **Wait For Element Visible** action waits for the specified element to become visible, but the element does not appear within the configured timeout period. As a result, the action fails. | Verify that the element is expected to appear, increase the timeout if the application loads slowly, and ensure the locator still matches the current application. | | No popup present | This error occurs when Avo Assure attempts to perform the Accept Popup or Dismiss Popup action, but no browser popup or alert is currently displayed. As a result, the requested popup operation cannot be completed. | Verify that the application triggers a popup before executing the action. Add appropriate synchronization or a step to confirm the popup is present before accepting or dismissing it. | | Unable to retrieve popup text | This error occurs when Avo Assure attempts to retrieve or verify the text of a browser popup, but the popup is unavailable, has already been closed, or cannot be accessed. As a result, the popup text cannot be retrieved or verified. | Ensure the popup is displayed and remains open before executing the action. Verify that the popup has not already been accepted or dismissed and retry the operation after adding appropriate synchronization. | | Input: \ is an invalid input | This error occurs when the **Verify Tooltip Text** action is executed with an empty, invalid, or unsupported input value. Since the expected tooltip text cannot be evaluated correctly, the verification fails. | Provide a valid expected tooltip text in the **Input Value** field before executing the verification. | | Tool tip Text \ mismatched with \ | This error occurs when the **Verify Tooltip Text** action compares the expected tooltip text with the actual tooltip text and detects a mismatch. As a result, the verification returns a False status. | Verify that the expected tooltip text exactly matches the actual tooltip text, including spaces, special characters, and letter case. | | Failed to launch the browser | This error occurs when the **Open Browser** action cannot start the selected browser because the browser or its driver is missing, or the browser and driver versions are mismatched. | Verify the browser is installed and the matching driver is present in the Avo Assure Client drivers folder. Update the browser/driver if versions differ and restart the Avo Assure Client. | | Error occurred when entering credentials | This error occurs when the Navigate with Authenticate action finds the Windows Security dialog but cannot enter the credentials or confirm the dialog. | Ensure the authentication dialog is in the foreground and the machine is not locked. Verify the username and password values and re-run the step. | | Remembered Credentials Present | This error occurs during Navigate with Authenticate when Windows has already saved credentials for the site, so the authentication dialog does not accept new input. | Remove the saved credentials for the site from Windows Credential Manager on the execution machine, then re-run the test step. | | Exception while ignoring the certificate | This error occurs when the ignore-certificate configuration is enabled but the browser certificate warning page could not be clicked through during Navigate with Authenticate | Verify the ignore certificate configuration value and the certificate warning page or install a valid certificate for the application under test. | | Wrong credentials and URL syntax \ | This error occurs when the Navigate with Authenticate action fails while processing the URL and credentials, typically because the input does not follow the expected format. | Provide the input in the format \;\;\ and ensure all three values are present and correctly separated. | | No previous page in browser history | This error occurs when the Navigate Back action is executed but the browser session has no previous page in its history. | Ensure at least one navigation step runs before Navigate Back. | | Driver object is null | This error occurs when a browser action such as Get Page Title, Verify Page Title, Get Current URL, or Maximize Browser is executed but no active browser session exists. | Ensure an Open Browser step runs successfully before this action and that no earlier step closed the browser. | | Failed to retrieve the page title | This error occurs when the **Get Page Title** action cannot read the title from the current browser session. | Verify the browser session is active and the page has loaded, then re-run the action. | | Expected title does not match actual title | This error occurs when the **Verify Page Title** action compares the input value with the actual page title and finds a mismatch. Expected and Actual values are printed on the console. | Verify the expected title in the Input Value column matches the page title exactly, including spaces and case and update the input. | | The actual URL does not match with expected | This error occurs when the **Verify Current URL** action compares the current browser URL with the expected value and detects a mismatch. | Verify the expected URL, ensure the application has finished navigating or redirecting, and update the input to match the final URL. | | Browser may already be closed or inaccessible | This error occurs when the **Close Browser** action fails because the browser window was already closed manually or the session is no longer accessible. | Ensure the browser session is still active when Close Browser runs and remove duplicate close steps from the test case. | | No sub windows to close / No sub-windows found or access denied. | This error occurs when the Close Sub Windows action is executed but only the main browser window is open. | Ensure the test flow actually opens sub windows/tabs before this step or remove the redundant action. | | No Cookies found | This error occurs when the **Clear Cache** action runs but no cookies exist in the current browser session. | Verify the application has been accessed in the session so cookies exist or remove the step if clearing is not required. | | Failed to Cache clearing | This error occurs when an unexpected exception is raised while clearing the browser cache or cookies. | Verify the browser session is active and responsive, then retry. Check the execution log for the underlying exception. | | Browser not available / Failed to retrieve browser name. | This error occurs when the **Get Browser Name** action is executed without an active browser session or an exception is raised while reading the browser name. | Ensure a browser is opened successfully before executing Get Browser Name. | | Zoom level setting failed. Wrong data is given : | This error occurs when the **Set Zoom Level** action receives a non-numeric zoom value or applying the zoom fails in the browser. | Provide a valid numeric zoom level in the Input Value column (for example 100 for 100%). | | Window \ not found / Current window handle not found / No handles found | This error occurs when the **Switch To Window** action cannot find a window matching the given number or title, the active window was already closed, or no window handles exist in the session. | Verify the target window/tab is open at that point in the execution and that the window number or title in the Input Value column is correct. | | Unable to retrieve browser PID. / Browser unavailable | This error occurs when the browser process ID cannot be retrieved to bring the browser window to the foreground, or the browser is unavailable. | Verify the browser session is active and was launched by Avo Assure. Restart the browser session if the process is no longer valid. | | Error with file operation | This error occurs for multiple actions: in Save File when the target file or folder cannot be accessed due to an IO or permission error, and in Upload File when the file specified in the Input Value column does not exist at the given path. | Verify the file path and name are correct (Upload File format: ;, multiple files separated by commas), the file/folder exists on the execution machine, and the user has read/write permission. | | Error while Saving file | This error occurs when an unexpected exception is raised while operating the Windows save dialog during the Save File action. | Verify the save dialog opens in the foreground, the path is valid, and the machine is not locked, then retry. | | Invalid number of coordinates given! | This error occurs for multiple actions: when the **Click** action (coordinate mode) or the Cell Click action is executed with coordinate input that does not contain exactly two comma-separated values. | Provide the coordinates as \,\ (for Click, percentages of the element, e.g. 50,50) with exactly two numeric values. | | Button name mismatched | This error occurs when the **Verify Button Name** action compares the input value with the actual button name (from text, value, or name attribute) and finds a mismatch. Expected and Actual values are printed on the console. | Verify the expected button name matches the actual button text exactly, including spaces and case, and update the input. | | There is no link text for the given element | This error occurs when the **Get Link Text** or **Verify Link Text** action is executed but the element has no visible text, no href attribute, and no text content. | Verify the captured element is a valid link containing text or an href attribute. Recapture the correct link element if needed. | | Link Text mismatched | This error occurs when the **Verify Link Text** action compares the input value with the actual link text and detects a mismatch. Expected and Actual values are printed on the console. | Verify the expected link text matches the displayed link text exactly, including spaces, special characters, and case. | | File type input Element is not Pressable, use uploadFile keyword instead. | This error occurs when the Press action is executed on a file upload control (input type=file), which cannot be pressed for file selection | Use the UploadFile action instead of the Press action to upload files. | | Check key syntax and failed focus of the element. | This error occurs when the Press action cannot focus and click the element, typically due to a stale element or invalid locator. | Verify the element is visible and focusable, confirm its locator is valid, add a wait for full page load, and recapture the element if its properties changed. | | Failed Element may not respond to double-click actions. | This error occurs when the **Double Click** action fails with an unexpected exception — the element may not support double-click interaction or its state prevented the action. | Verify the element supports double-click and is visible and stable during execution. Add a wait step or recapture the element and retry. | | Right click failed | This error occurs when the **Right Clic**k action fails with an unexpected exception — the element or browser session prevented the context-click. | Verify the element is visible, stable, and supports the context menu. Ensure no overlay blocks the element and retry. | | Not able to click on the element to upload file | This error occurs when the This error occurs when the **Upload File** action cannot open the file selection dialog because the upload element is not clickable or the dialog does not appear within the specified wait time. | Verify the upload control is visible and clickable, increase the dialog wait time (third input parameter), and ensure no other window steals focus. | | Invalid Input: Index out of range | This error occurs when the **Select Value By Index** action targets a custom list (li), tab list, or menu control and the given index exceeds the number of available options. | erify how many options the list contains at execution time and provide an index within that range. | | Error selecting li/tablist/menuitem by index/value | This error occurs when an unexpected exception is raised while clicking the option of a custom list (li), tab list, or menu control located by index or by text during Select Value By Index or Select Value By Text. | Verify the list stays open and stable during selection, add a wait step for dynamic lists, and recapture the element if the control re-renders. | | Invalid input : Give a number as a input | This error occurs when the Select Value By Index action receives a non-numeric value where a numeric index is required. | Provide a valid whole number as the index in the Input Value column. | | Element not found with given value input / Value, not found | This error occurs for multiple actions: when Select By Value, Select By Absolute Value, or Select Value By Text (including table dropdowns) cannot find any option whose value or text matches the given input. | Verify the input matches an option's value/text exactly, including spaces and case, and that the list is fully loaded before selection. | | Input did not match with data list | This error occurs when the **Select Value By Text** action compares the input against the list of available option texts and finds no match. The available values are shown for reference. | Choose the expected value from the option list shown in the console output and update the Input Value column to match it exactly. | | Count mismatched | This error occurs when the **Verify Count** action compares the expected count from the Input Value column with the actual number of options in the dropdown/listbox and finds a difference. | Verify the expected count and ensure the list is fully loaded before executing the verification. | | Provided input not present in element | This error occurs when the **Get All Values** or **Verify All Values** action checks for a given value among the dropdown/listbox options and it is not present. | Verify the value exists in the list at execution time. Add a wait step if the options load dynamically. | | Invalid Error: Select not provided/found in input | This error occurs when the **Get Selected** action runs on a table cell but no select (dropdown) element is provided or found in the specified cell input. | Verify the input identifies a cell that contains a select/dropdown control and include the select tag in the input where required. | | Control failed to switch to frame/iframe path | his error occurs when the @Custom element flow attempts to switch into the frame/iframe indicated by the captured element path, but the switch fails — the frame index is wrong or the frame has not loaded. | Verify the frame/iframe structure has not changed since capture. Recapture the @Custom element if the page structure changed, and increase the timeout configuration for slow-loading frames. | | Custom object not found (ERR\_CUSTOM\_NOTFOUND) | This error occurs when no element matching the @Custom criteria (element type, visible text, and index) is found within the element load timeout, including searches inside iframes. The keyword continues without an element, so the step typically fails afterwards with an element identification error. | Verify the element type, visible text, and index are correct and the element is present at execution time. Increase the element load timeout for slow pages and confirm the preceding VerifyExists step passed | | Negative element index (ERR\_NEGATIVE\_ELEMENT\_INDEX) | This error occurs when the @Custom element is used with a negative index value; the index must be zero or positive. | Provide a zero-or-positive index in the @Custom element input. | | Number format exception (ERR\_NUMBER\_FORMAT\_EXCEPTION) | This error occurs when the index provided for the @Custom element is not a valid number. | Provide a valid numeric index in the @Custom element input. | | Actual text does not match expected | This error occurs when an unexpected exception is raised while the Verify Element Text action compares the values, typically due to an invalid element or browser session. | Verify the element is present and stable at execution time and retry. Check the execution log for the underlying exception. | | Element can't accessed ,error with browser | This error occurs when an unexpected exception is raised while verifying the tooltip text — the element could not be accessed or the session was disrupted. | Verify the element is present and hoverable and the browser session is active, then retry. | | Not able to fetch the dynamic ag-grid tooltip text | This error occurs when the Get AG-**Grid Tooltip Text** action performs the mouse hover on the grid cell but the dynamically appended tooltip element could not be captured from the DOM. A related message, Please provide valid input, occurs when the cell coordinates are missing or not in the expected format. | Verify the grid cell renders a tooltip on hover and the coordinates are correct and in the expected format, and ensure the grid is fully loaded. | | Alert Text mismatched | This error occurs when the **Verify Popup Text** action compares the input value with the alert text and finds a mismatch. Expected and Actual values are printed on the console; the step fails. | Verify the expected popup text in the Input Value column matches the alert text exactly, including spaces and case, using the Expected/Actual values on the console. | | Object not found: Radio button/Checkbox/Textbox not found inside the cell | This error occurs for multiple actions: when Select Radio Button, Select/Unselect Checkbox, or Get Status targets a grid (AG-Grid) cell and the cell does not contain an input element of the expected type. | Verify the row/column input points to the cell that actually contains the radio button or checkbox, and recapture the grid element if its structure changed. | | Invalid input: Row number more than row count | This error occurs for multiple actions: when a grid operation (Select Radio Button, Select/Unselect Checkbox, Get Status, or table cell keywords) receives a row index larger than the number of rows present in the resolved grid region. | Verify how many rows the grid/table contains at that point in the execution and provide a row number within that range. | | Invalid input: Col number more than col count | This error occurs for multiple actions: when a grid or table operation (Select Radio Button, Select/Unselect Checkbox, Get Status, Get/Verify Cell Value, or Cell Click) receives a column index larger than the number of cells in the target row. | Verify how many columns the row contains and provide a column number within that range. | | Text is not present | This error occurs when the **Verify Text Exists** action searches the page (including frames and iframes) for the given text and finds zero occurrences. | Verify the text is displayed on the page at execution time, including correct spelling, case, and any dynamic content that may change the text. | | Error occurred while verifying text | This error occurs when an unexpected exception is raised while the **Verify Text Exists** action counts the text occurrences on the page. | Verify the browser session is active and the page is fully loaded, then retry. Check the execution log for the underlying exception. | | Error fetching row count / Error fetching column count | This error occurs when the **Get Row Count** or **Get Column Count** action cannot compute a valid count from the table or grid, typically because the table structure is not recognized. | Verify the captured element is the table/grid itself and the table is fully loaded. Recapture the element if the structure changed. | | Element is hidden | This error occurs for multiple actions: when a table/grid keyword (Get Row/Column Count, Get/Verify Cell Value, Cell Click, Right/Double Cell Click, Get Cell Tooltip, Get Row/Column Data, Verify Table Value, scrolling) targets a table that exists in the DOM but is not visible on screen. | Verify the table is rendered and visible at execution time, scroll it into view, and add a wait/synchronization step for pages that render the table late. | | Not a correct Syntax for row using name | This error occurs for multiple actions: when Get/Verify Cell Value, Cell Click, Right Cell Click, or Double Cell Click uses row-by-name addressing and the input does not follow the expected syntax. | Provide the row/column condition in the supported format for name-based addressing (for example :;) as described in the keyword documentation. | | Unable to retrieve the cell value. Please check if the cell value is present on the page. | This error occurs when the **Get Cell Value** or **Verify Cell Value** action locates the cell but cannot read a value from it. | Verify the cell actually contains a value at execution time and the row/column input points to the correct cell. | | Invalid input: Column not found / Column not found | This error occurs for multiple actions: when Get/Verify Cell Value or Cell Click addresses a column (by number or name) that does not exist in the table. | Verify the column number or name against the actual table structure and update the input. | | Cell value not found. Check table, row, and column | This error occurs when an unexpected exception is raised while reading the cell value, typically because the table, row, or column reference is invalid. | Verify the table element and the row/column input are correct, and ensure the table is fully loaded before the action | | No cell tool tip present for the cell | This error occurs when the **Get Cell Tooltip** action targets a cell that does not render any tooltip. | Verify the cell actually shows a tooltip on hover and the row/column input points to the correct cell. | | Invalid input: No such columnheader with name: exists | This error occurs when the **Right Cell Click** or **Double Cell Click** action addresses a column header by name and no header with that name exists in the grid | Verify the column header name matches the grid exactly, including spaces and case. | | Error in fetching Row number \ | This error occurs when the **Get Row Number By Text** action cannot resolve a valid row number for the given text. | Verify the text exists in the table and the input follows the expected format for the keyword. | | Could not find the text by Row number, or the text is not present in the table \ | This error occurs when the **Get Row Number By Text** action searches the table for the given text and does not find it. | Verify the text is present in the table at execution time, including exact spelling, case, and spaces. | | Invalid input: "times" should be a non-zero integer | This error occurs when the **Vertical Scroll** or **Horizontal Scroll** action receives a scroll count that is not a non-zero integer. | Provide a non-zero whole number for the number of scrolls in the Input Value column. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.avoautomation.com/avo-assure/error-logs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.