Troubleshooting

Start troubleshooting with the first Block that did not do what you expected. Most failures come from page state, selectors, timing, missing access, variables, or output handoff.

Workflow does not run

Check the Flow before checking the website. Make sure the Blocks are connected, required settings are filled, and the run mode matches what you are trying to test. If the run starts and then stops, inspect the first failing Block instead of changing later Blocks first.

Browser action fails

If a browser action fails, check what the page looked like immediately before that Block ran. The page can load the wrong state, hide the target element, match the wrong selector, or interrupt the Flow with a login or access step.

Fix one browser state issue at a time. Add a wait only when the page genuinely needs more time. Change a selector only after confirming the element changed.

Extraction returns empty data

Empty extraction usually means the Flow reached the wrong page state, selected the wrong part of the page, or ran before the content appeared. Check whether the content is visible in the browser, then inspect the extraction Block's target and output.

If one field is empty but other fields work, the page can be missing that field for some rows. If every row is empty, start with the target selector or the Block that opened the page.

Cloud run differences

If a Flow works locally but fails in a Cloud Run, compare the earliest visible difference. The target site can show different content, require a different login state, load slower, or block hosted browser traffic. Do not rewrite the whole Flow first. Find the first Block where local and cloud behavior diverge.

Missing output