Runs in Browserflow Cloud are limited to 2 minutes. If your flow takes longer than the limit, see if you can break the flow up into smaller pieces.
For example, suppose that you want to scrape a long list of items that each has its own detail page. If your flow loops through the items by clicking into each item's detail page and going back, the run will likely take too long.
Instead, you can break this up into two steps:
Collecting a list of URLs
Automating each URL
You can store the list of URLs in a Google Sheet and use the Loop Spreadsheet Rows command to loop through the sheet. In the cloud, each row will execute in a separate run so the 2-minute limit will apply for each URL rather than for all the URLs combined.
If your flow cannot be broken up, please contact support for troubleshooting and additional options.
Command interrupted by navigation
If a page navigation occurs while a command is executing, the flow will fail because the execution context is destroyed.
Common scenarios for when this occurs and how to fix it:
Visiting a page that redirects
If you visit a page that redirects, you need to wait for the redirects to complete before continuing.
Add a Wait command right after Visit to make sure that all redirects are completed before the flow continues. Try a wait time of 3 seconds and increase it if it's not enough.
Clicking a button or link that loads a new page
If you click on a button/link or press a key (e.g. Enter) that loads a new page, you need to make sure that the page loads before continuing.