Error causes and solutions for elements in Window applications and browsers

When creating workflows in akaBot Studio, there are cases where elements are captured successfully during the setup of activities like click or text input, but errors like "element not found" occur during execution, or the element specification itself fails. Here are some examples of causes and solutions for element-related errors.

Table of Contents

[Workflow Creation] Both Browser and Window Application

• Case: The value of the element you want to capture changes every time it starts

[Workflow Creation] Browser

• Case 1: No extension installed (Chrome, Firefox, Edge)
• Case 2: Elements that appear dynamically (e.g., Flash) do not have tags assigned
• Case 3: Unable to operate screens opened without specifying a URL (Chrome, Firefox, Edge)

[Workflow Creation] Window Application

• Case 1: Application is old (UIA3 cannot capture elements correctly)
• Case 2: The program that makes up the application is not structured

[Workflow Creation] Other

[Workflow Execution] Both Browser and Window Application

• Case 1: The desired location has not finished loading during execution (slow network environment, freeze, etc.)
• Case 2: If the element appears dynamically, it can only be captured when it is displayed on the screen
• Case 3: The target screen is visually in the foreground but not recognized as the target internally

1. [Workflow Creation] Both Browser and Window Application

Case: The value of the element you want to capture changes every time it starts

Example Solutions:

• Make the target unique by specifying the element with wildcards or by checking another element.
• Change parts that differ in each startup (e.g., ClassName, file name) to wildcards "*".
• Uncheck changing elements and check fixed elements instead.
• If AutomationID is checked during selector capture, check other values like IndexInParent.

2. [Workflow Creation] Browser

Case 1: No extension installed (Chrome, Firefox, Edge)

Example Solutions:

• Install extensions compatible with each browser.
• Confirm operation procedures here.

Case 2: Elements that appear dynamically (e.g., Flash) do not have tags assigned Note: Adobe Flash Player support ended in late 2020

Example Solutions:

• Try solutions listed in the "Other" section below.

Case 3: Unable to operate screens opened without specifying a URL (Chrome, Firefox, Edge)

Example Solutions:

• Try solutions listed in the "Other" section below.

3. [Workflow Creation] Window Application

Case 1: Application is old (UIA3 cannot capture elements correctly)

Example Solutions:

• Change the "AutomationBase" property from "UIA3" to "UIA2".

Case 2: The program that makes up the application is not structured

Example Solutions:

• Try solutions listed in the "Other" section below.

4. [Workflow Creation] Other

If the solutions listed in sections 1 to 3 do not work, try the following (examples):

• Use the "Click Image" activity to set the element you want to capture as an image.
• Use the "Send Hotkey" activity to utilize application-compatible shortcuts (e.g., "Ctrl" + "C").
• (For browsers) Use the "Inject Javascript" activity to operate via Javascript.

5. [Workflow Execution] Both Browser and Window Application

Case 1: The desired location has not finished loading during execution (slow network environment, freeze, etc.)

Example Solutions:

• Use the "Element Exists" activity to confirm the desired location has finished loading.
• Avoid proceeding to the next operation until loading is complete.
• Place a "Delay" activity for a few seconds (2-5 seconds).

Case 2: If the element appears dynamically, it can only be captured when it is displayed on the screen

Note: For example, elements in a tree structure become capturable when the "show next element" is clicked.

Example Solutions:

• Display the element on the screen before executing the desired operation.

Case 3: The target screen is visually in the foreground but not recognized as the target internally

Example Solutions:

• Make the target explicit.
• Insert an "Attach Browser" or similar activity to explicitly select the browser/application to operate (bring it to the foreground).