Troubleshooting

This topic describes some unexpected scenarios, and explains what to do when they occur.

Runtime errors

If you try to run a script and it fails immediately, open the %localappdata%\VEFTDesign\CodelessAgent\Logs\codeless.executer.log file for more details.

The table below explains what to check for different errors that might occur when running a script:

Error message What to do

No item detected for class <class>.

  • Make sure the application was launched correctly.
  • Make sure the application is in the correct state.
  • Make sure the object is visible on the screen.
Detection not unique for class <class>.
  • Make sure the application was launched correctly.
  • Make sure the application is in the correct state.
  • Make sure there is only one object of the required class.

Back to top

Verification misled by misspelling indication

Running a Verify step on text may fail if the text is displayed with a misspelling indication, such as a red line under the text.

Use one of the following workarounds:

  • Disable spell checking in your browser or application.

  • Before the Verify step, add a step that clicks another location, to remove the focus from the text and clear misspelling indication.

Example: The following example adds a step before the Verify step to move the focus away.

Copy code 
Click the profile
Type "naame" into "Username" input
Click the "Username" text 
Verify that the value of "Username" input is "naame"

Back to top

Logs

If any error occurs, for which you need additional information, check the %localappdata%\VEFTDesign\CodelessAgent\Logs folder for more details about the error.

Back to top