Interact step errors

The errors on this page can occur with interact steps such as Click element, Enter text, and Press key(s).

Element not found on page

Error: Your chosen selectors have failed to find any content on page. The error can also appear as Could not find the requested element, Error in all rows of loop, your chosen selectors have failed to find any content on page, or Node is either not clickable or not an HTMLElement on row 1.

Problem: The element selected in the step wasn't on the page when the automation ran. Common causes:

• The page didn't finish loading before the step fired.
• The page changed since the automation was set up, and the selector no longer matches.
• The automation is on a different page from the one the selector was built against.
• A cookie window is covering the page. Cloud runs start in a fresh browser, often in another country, so a site shows a cookie window there that you never see in your own signed-in browser, and the click lands on the window instead of the element.

Fix: Re-select the element using the selector tool inside the failing step. If the page is slow to load, increase the minimum wait time in the step's configure scraper options. If the run's live view shows a cookie window, add a Click element step after Go to page that matches the window's button by its text, with Optional click on, so the window is closed when it appears and skipped when it doesn't: see automate closing cookie windows, notification prompts and pop-ups.

2FA code not accepted

Error: The site reports the code as incorrect or expired after the Enter text step types the [totp-code] token, and the run fails at the next step with Element not found on page because it never left the verification page.

Problem: The code the Generate authenticator code step produced does not match what the site expects. Common causes:

• The 2FA secret saved with the credential is not the one the site is using. This happens when the key was copied after the first code was verified, or when 2FA was set up again later and the site issued a new key.
• The code was typed too quickly for the site's field to accept it, or typed into the wrong field.
• The site asked for a different kind of check this time, such as a code sent by email or SMS, which an authenticator code cannot answer.

Fix: Turn the site's authenticator method off and on again, copy the key it shows before verifying the first code, and paste it into the credential's 2FA secret field by editing the credential. Keep the Generate authenticator code step directly before the Enter text step, keep the step's default typing delay, and check the step selects the verification field. For a code sent by email or SMS, see codes sent by SMS or email. A worked login is in automate 2FA login for your Instagram bot.

Text is not iterable

Error: Text is not iterable.

Problem: An Enter text or Press key(s) step has an empty Text field.

Fix: Set Text on the step to a value, or pass data in via Insert data.

Character not recognised

Error: (Something) is not a character.

Problem: The text contains a character axiom.ai doesn't recognise as a single character. This often happens with copy-pasted content that includes hidden formatting or zero-width characters.

Fix: Look at the text in the failing step and replace any unusual characters. If the text was copy-pasted, retype it manually to strip any invisible metadata.

Browser closed

Error: Browser closed. The error can also appear as Automation could not continue as all open browser tabs were closed.

Problem: The browser or all of its tabs were closed during the run.

Fix: Keep the browser open while the automation runs. To run unattended without this risk, run the automation in the cloud instead of on the desktop.