Generic Actions

The following are common errors that can occur while using frequently used actions:

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.
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.
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.
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 <start row - end row>.
Invalid Input for Evaluate Action	An Evaluate expression attempted division by zero.	Validate the denominator before performing division.
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	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: <file path>;<page number>;<start string>;<end string>;<text/image/all>. 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.
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.
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.
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.
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.
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.
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.
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: <Row>;<Column>;<header/body>(optional);<left/right>(optional);<row_attr>(optional);<col_attr>(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.
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	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.
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.
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.
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 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.