Runtime errors

The errors on this page occur during an automation run.

Selectors found no content

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

Problem: The element your step is configured to interact with isn't on the page. Common causes:

• The selector is inconsistent across pages.
• The automation is on the wrong page when the step runs.
• The page hasn't finished loading.
• The site is blocking the automation.

Fix: Confirm the element is on the page when you load it manually, and that the automation is on the correct page when the step runs. To handle slow-loading pages, increase the minimum wait time in the step's configure scraper options. If the site is blocking the automation, try the desktop app or bypass bot detection. If none of these resolve the issue, contact support.

The automation is logged out when scheduled or triggered on the desktop app

Error: Usually Selectors found no content or Could not find the requested element on the first step after a login page, when the same automation works with Run w/ desktop app.

Problem: A run the desktop app starts on its own, from the scheduler or an API trigger, has no browser session, so it does not have your Chrome cookies, even if Chrome is open. The site shows its login page instead of the page the step expects.

Fix: Turn on store cookies for the automation and resync them, or add a Log in with credentials step so the run signs in itself. If it worked before and has stopped, the stored cookies have most likely expired: open the automation's settings and click Resync cookies.

Browser closed

Problem: The browser was closed while the automation was still running.

Fix: Don't close the browser during a run. If the browser closes on its own, contact support.

Execution context was destroyed, most likely because of a navigation

Error: Execution context was destroyed, most likely because of a navigation.

Problem: The browser navigated away from the page or tab the automation was working on.

Fix: Don't switch tabs while a run is in progress. If the automation needs to follow a link that opens in a new tab, handle the switch with the Switch browser tab step.

Runtime errors on long automations

Problem: Larger automations can hit single-run runtime limits or concurrency limits.

Fix: Break large jobs into smaller batches. For example, split a 10,000-record scrape into ten runs of 1,000 records each. This reduces the chance of a single error costing you the whole job and makes restarts much faster. For runtime and concurrency limits per plan, see the pricing page.