Element Not Found Errors
This error means the selector did not match any element on screen within the timeout period. Follow these steps in order to resolve it.
Step 1 — Increase the Timeout
In Properties → Timeout, change from 00:00:30 to 00:01:00. Some apps load slowly, especially on first launch.
Step 2 — Re-pick the Element
The app UI may have changed since you recorded. Click the wand icon in the selector field and select the element again.
Step 3 — Add a Wait For Element Activity
Place a Wait For Element activity before the failing activity. This explicitly waits for the element to exist before trying to click or read it.
Step 4 — For Web Apps: Add Wait For Page Load
Use Wait For Page Load to ensure the page has finished rendering after a navigation event.
Step 5 — Fix Dynamic Selectors
Open the Selector Editor (wrench icon in Properties). Look for dynamic attributes that change on every page load:
| Dynamic Attribute | Example | Fix |
|---|---|---|
| Auto-generated IDs | id="ember123", id="react-select-5" | Remove from selector, or use partial match: id~=react-select |
| Session-specific classes | class="ui-id-7" | Remove from selector entirely |
| Keep stable attributes | name, placeholder, aria-label, data-testid | Prefer these over auto-generated values |
Step 6 — Desktop Apps: Check Window State
Make sure the target application is fully loaded and not behind another window. Add a Delay of 1–2 seconds if necessary, or use Activate Window to bring the app to the foreground.