Runtime errors
The errors listed below occur during a run.
# Runtime errors
Your chosen selectors have failed to find any content on page / element not found
Alternative(s): "could not find the requested element", "error in all rows of loop", could not find the requested element", "error in all rows of loop, your chosen selectors have failed to find any content on the page".
Problem: the page element that you have selected a step to work with could not be found on the page. There are numerous reasons that may cause this, including: inconsistent selectors between pages, the automation being on the wrong page, the page not loading in time, or the automation being blocked.
Fix: confirm that the element that the automation is to work with is on the page when you load the page and that the automation is set to run on the correct page. To prevent the automation failing when the page takes a few seconds to load, use the configure scraper option in the step to add a minimum wait time. For automations that are blocked, this can usually be circumvented by using the desktop application. If you are unsure, or these steps do nto work, contact us (opens new window).
# Browser closed
Problem: the browser was closed while the automation was running, causing the automation to fail.
Fix: avoid closing the browser during automation runs, if this persists, contact us (opens new window).
# Execution context was destroyed, most likely because of a navigation.
Problem: the browser window may have navigated away from the window that the automation was working on.
Fix: prevent switching tabs from the tab that the automation is running, use the "Switch browser tab" step if you require the automation to switch tabs, such as when a link opens in a new tab.
# Runtime errors when running long automations
Problem: some larger jobs may run into issues with the runtime limits placed on single-run automations, and limits on concurrency.
Fix: consider breaking larger automations into smaller batches - for example, if you wish to scrape 10,000 records, do this in 10 runs of 1,000 records. This will reduce the chances of errors arising and makes it simpler when an error does occur as the whole automation would not need to be run again. For more information on runtime limitations and concurrency, see Pricing (opens new window).
# Chromium crashing due to memory issues
Problem: in some long or resource heavy automations it is possible that the browser will crash due to memory issues.
Fix: in addition to the fixes mentioned in Runtime errors when running long automations, the Browser restart step can be inserted into your automation to restart the automation and clear the memory to prevent the browser from crashing. We recommend reading more about this step before inserting it.