Run and debug
Debug failed browser automation in AutoTapper
Use AutoTapper execution logs to find whether a browser automation failure came from selectors, navigation timing, invalid tabs, or missing variables.
Read the failing step first
Do not start by editing everything. Open the execution log and identify the first step that actually failed or behaved unexpectedly.
Common failure groups
- Selector missing or wrong target matched.
- Page navigation finished later than expected.
- The selected tab or page context no longer exists.
- A variable, extracted value, or loop row is empty.
Practical debugging habit
Fix one failure class at a time, then rerun only the relevant section. This keeps the workflow easier to reason about.
